Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b25591eb637c5d11e3851b8b4972fc517aaf238655efd0f3f112e4d9446720f

Tx prefix hash: 489692b891cd5960cab0b582a1a1b74da8615c8d42991faac09ce622b50e2e6c
Tx public key: 55b1a31a4cc4824b964e7bcacfe708d3c6f59495f8b2ab5bdb38494de41a0ac3
Timestamp: 1764878496 Timestamp [UCT]: 2025-12-04 20:01:36 Age [y:d:h:m:s]: 00:018:09:11:30
Block: 1426506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13144 RingCT/type: yes/0
Extra: 0155b1a31a4cc4824b964e7bcacfe708d3c6f59495f8b2ab5bdb38494de41a0ac302110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d4118e50b68d51ca0951077651f69e916bc2034a66efe280d4a92d02d5da74e 0.600000000000 1915197 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": 1426516, "vin": [ { "gen": { "height": 1426506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d4118e50b68d51ca0951077651f69e916bc2034a66efe280d4a92d02d5da74e" } } ], "extra": [ 1, 85, 177, 163, 26, 76, 196, 130, 75, 150, 78, 123, 202, 207, 231, 8, 211, 198, 245, 148, 149, 248, 178, 171, 91, 219, 56, 73, 77, 228, 26, 10, 195, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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