Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5e9866c029f4f6b8ae0510c70578ddf7ffce3b4b5e6d58ce8ecec26d034e17b

Tx prefix hash: 5870b85f305a63ce5a890cfe7d17d22805c326f5488f8cf6a1b6e8225a000215
Tx public key: e5d5e6e80fcc347794f9cb59ca2301c00e0c4762237782734ae1db6c18d2bfc6
Timestamp: 1718177713 Timestamp [UCT]: 2024-06-12 07:35:13 Age [y:d:h:m:s]: 01:159:18:18:26
Block: 1042455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372751 RingCT/type: yes/0
Extra: 01e5d5e6e80fcc347794f9cb59ca2301c00e0c4762237782734ae1db6c18d2bfc60211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 160e1cedee829360d507d374a69325481bb1d40378d20c36568932eacd40940e 0.600000000000 1511380 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": 1042465, "vin": [ { "gen": { "height": 1042455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "160e1cedee829360d507d374a69325481bb1d40378d20c36568932eacd40940e" } } ], "extra": [ 1, 229, 213, 230, 232, 15, 204, 52, 119, 148, 249, 203, 89, 202, 35, 1, 192, 14, 12, 71, 98, 35, 119, 130, 115, 74, 225, 219, 108, 24, 210, 191, 198, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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