Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: df5592faded36bdd369e3aafd9cb8afa1684968f563496804fa42a5b92821efb

Tx prefix hash: a4b4bf3df63147c9dc9554f382f03444f176434b60af71a75a6a953df47d25bb
Tx public key: c636ca6a51443fe54ea6e89a8ec86c93465e9b4c4456880a70748dd52acd5f1a
Timestamp: 1646842730 Timestamp [UCT]: 2022-03-09 16:18:50 Age [y:d:h:m:s]: 03:010:19:21:17
Block: 454794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 787882 RingCT/type: yes/0
Extra: 01c636ca6a51443fe54ea6e89a8ec86c93465e9b4c4456880a70748dd52acd5f1a0211000000054a0f5013000000000000000000

1 output(s) for total of 19.102005060000 dcy

stealth address amount amount idx
00: b4119a022f7bc04bd9c9e16e21260af8e0ce01ca3e3d8fc89926cae083d3b2c7 19.102005060000 870513 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 454804, "vin": [ { "gen": { "height": 454794 } } ], "vout": [ { "amount": 19102005060, "target": { "key": "b4119a022f7bc04bd9c9e16e21260af8e0ce01ca3e3d8fc89926cae083d3b2c7" } } ], "extra": [ 1, 198, 54, 202, 106, 81, 68, 63, 229, 78, 166, 232, 154, 142, 200, 108, 147, 70, 94, 155, 76, 68, 86, 136, 10, 112, 116, 141, 213, 42, 205, 95, 26, 2, 17, 0, 0, 0, 5, 74, 15, 80, 19, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8