Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 479bd2b5da08068978b5324e292b55b4259f600a5635d9774ae5ecc13e5ca0af

Tx prefix hash: 88dcab78dcfe747b576d5b1e24289e181f13a260be7e112b924a5bfe518235cd
Tx public key: e348aab2eafdbb48e8932149adf465dbd477bbcf4942e6b9920f31b0e6a5b16e
Timestamp: 1713245560 Timestamp [UCT]: 2024-04-16 05:32:40 Age [y:d:h:m:s]: 00:357:08:06:04
Block: 1001541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255472 RingCT/type: yes/0
Extra: 01e348aab2eafdbb48e8932149adf465dbd477bbcf4942e6b9920f31b0e6a5b16e02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66cb641ff3ec3bb6a9ea08333f92a443f84a9ebe15d104b616e91c3d9c5b8d35 0.600000000000 1462047 of 15

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": 1001551, "vin": [ { "gen": { "height": 1001541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66cb641ff3ec3bb6a9ea08333f92a443f84a9ebe15d104b616e91c3d9c5b8d35" } } ], "extra": [ 1, 227, 72, 170, 178, 234, 253, 187, 72, 232, 147, 33, 73, 173, 244, 101, 219, 212, 119, 187, 207, 73, 66, 230, 185, 146, 15, 49, 176, 230, 165, 177, 110, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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