Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57e05950245882d160969c7afe601987ae172d464c6186b5331a780d6238cb33

Tx prefix hash: d9f2abefcb7588bc9dcbf0beb724d7994b52de869171c6c8ff5736d5801df83c
Tx public key: e7bba2dccf48d6e1d3027d27ce7e5d4c711a193311d9d701b7c6fd29b0e83117
Timestamp: 1763910416 Timestamp [UCT]: 2025-11-23 15:06:56 Age [y:d:h:m:s]: 00:004:13:44:17
Block: 1418467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3274 RingCT/type: yes/0
Extra: 01e7bba2dccf48d6e1d3027d27ce7e5d4c711a193311d9d701b7c6fd29b0e83117021100000007d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bc8f5cc73109af9d04437969e8d38cdc68519caa4553be10a0d115f0119b9b7 0.600000000000 1906998 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": 1418477, "vin": [ { "gen": { "height": 1418467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bc8f5cc73109af9d04437969e8d38cdc68519caa4553be10a0d115f0119b9b7" } } ], "extra": [ 1, 231, 187, 162, 220, 207, 72, 214, 225, 211, 2, 125, 39, 206, 126, 93, 76, 113, 26, 25, 51, 17, 217, 215, 1, 183, 198, 253, 41, 176, 232, 49, 23, 2, 17, 0, 0, 0, 7, 214, 225, 157, 124, 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