Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b351eee9f1563ddef739bdb97139ec34af3e965e0251c004259ac3cf1c8f0ed

Tx prefix hash: 9f91e8a671f75b916ad28b7486c28933e53e71714e69d495a9cc16871e4338dd
Tx public key: 071b020b9f14c012969e739f5e64c924e2ba37ee1b7b76b5886b1a8c8fdc6482
Timestamp: 1727713813 Timestamp [UCT]: 2024-09-30 16:30:13 Age [y:d:h:m:s]: 00:114:07:37:18
Block: 1121511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81686 RingCT/type: yes/0
Extra: 01071b020b9f14c012969e739f5e64c924e2ba37ee1b7b76b5886b1a8c8fdc648202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41d18087dbba0b24820ddf3271526f17a53c205c77a4dce915ea6ba565c7616b 0.600000000000 1603796 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": 1121521, "vin": [ { "gen": { "height": 1121511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41d18087dbba0b24820ddf3271526f17a53c205c77a4dce915ea6ba565c7616b" } } ], "extra": [ 1, 7, 27, 2, 11, 159, 20, 192, 18, 150, 158, 115, 159, 94, 100, 201, 36, 226, 186, 55, 238, 27, 123, 118, 181, 136, 107, 26, 140, 143, 220, 100, 130, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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