Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc2e6ae75e9568c767ca931c0909b6f03cdf28f3fdd419473143f9f31a9e99b0

Tx prefix hash: 4aa67a4d9c9129d9cc0695847d3839696fd1419f71ddfae3d41fce676e6e834d
Tx public key: 6b62517bd327120447acee0d5cdc9963afefeb8c96a5bae13444a8918591cbfa
Timestamp: 1752301182 Timestamp [UCT]: 2025-07-12 06:19:42 Age [y:d:h:m:s]: 00:132:18:26:04
Block: 1323729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93583 RingCT/type: yes/0
Extra: 016b62517bd327120447acee0d5cdc9963afefeb8c96a5bae13444a8918591cbfa021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5a1e00140543d1b37f2888e098e998ed74c366b0cbdd155ac33eb60ed0b11fd 0.600000000000 1811468 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": 1323739, "vin": [ { "gen": { "height": 1323729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5a1e00140543d1b37f2888e098e998ed74c366b0cbdd155ac33eb60ed0b11fd" } } ], "extra": [ 1, 107, 98, 81, 123, 211, 39, 18, 4, 71, 172, 238, 13, 92, 220, 153, 99, 175, 239, 235, 140, 150, 165, 186, 225, 52, 68, 168, 145, 133, 145, 203, 250, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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