Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 959c0c71d833ea95fbc9173f2aaa75c06d608e020ff5526e9397953706055ca5

Tx prefix hash: 3fe55b5cd13f056c80b6cde45e4352db738282d8d215dc0c2b2d24e292ed2fe7
Tx public key: 4dd75c4cefb5e5c9863101c0f713fc5a061e3ec9b14d49730c8db15a5bc86f94
Timestamp: 1765581463 Timestamp [UCT]: 2025-12-12 23:17:43 Age [y:d:h:m:s]: 00:010:04:19:23
Block: 1432315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7289 RingCT/type: yes/0
Extra: 014dd75c4cefb5e5c9863101c0f713fc5a061e3ec9b14d49730c8db15a5bc86f9402110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5e30179f4e16382550078911afc87fecfffdb09b721b02b0d3a623891945402 0.600000000000 1921094 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": 1432325, "vin": [ { "gen": { "height": 1432315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5e30179f4e16382550078911afc87fecfffdb09b721b02b0d3a623891945402" } } ], "extra": [ 1, 77, 215, 92, 76, 239, 181, 229, 201, 134, 49, 1, 192, 247, 19, 252, 90, 6, 30, 62, 201, 177, 77, 73, 115, 12, 141, 177, 90, 91, 200, 111, 148, 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