Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98c52f2c7f980641178bfcb558ae5c539d7e2ec0b2d91e6374f8257bf03b33ca

Tx prefix hash: 417f0fdddac098d22c0e7132289f2666b985fc8271b5d2c7dad78af8e07cf106
Tx public key: 9a850ecdf9c712b4e2086d9c2db47a806087c7c482884dd53e73bc91eee1de6e
Timestamp: 1754672593 Timestamp [UCT]: 2025-08-08 17:03:13 Age [y:d:h:m:s]: 00:172:11:30:59
Block: 1342931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122296 RingCT/type: yes/0
Extra: 019a850ecdf9c712b4e2086d9c2db47a806087c7c482884dd53e73bc91eee1de6e02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae594da12771bb2aa24ca4b088a259ee058a0389caf91fd56deca66c840193fc 0.600000000000 1830766 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": 1342941, "vin": [ { "gen": { "height": 1342931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae594da12771bb2aa24ca4b088a259ee058a0389caf91fd56deca66c840193fc" } } ], "extra": [ 1, 154, 133, 14, 205, 249, 199, 18, 180, 226, 8, 109, 156, 45, 180, 122, 128, 96, 135, 199, 196, 130, 136, 77, 213, 62, 115, 188, 145, 238, 225, 222, 110, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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