Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac413434a7645b28666c1b42b4123a90b23be85e377267e9b47cd65f821f3e08

Tx prefix hash: bd4dde05d59aab532b41baa2f267be50407e0b85710082ccf113eeb10d87721d
Tx public key: eb608069415e0c063a7d5680453801c9c9074e6096df86da6638aa2daf629213
Timestamp: 1734182403 Timestamp [UCT]: 2024-12-14 13:20:03 Age [y:d:h:m:s]: 00:188:15:08:51
Block: 1175040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134472 RingCT/type: yes/0
Extra: 01eb608069415e0c063a7d5680453801c9c9074e6096df86da6638aa2daf6292130211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7de9d4e6eb3ad9a1e867b94baaf6df7558c5a247ace7d0e9a92337cde67e14c5 0.600000000000 1661267 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": 1175050, "vin": [ { "gen": { "height": 1175040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7de9d4e6eb3ad9a1e867b94baaf6df7558c5a247ace7d0e9a92337cde67e14c5" } } ], "extra": [ 1, 235, 96, 128, 105, 65, 94, 12, 6, 58, 125, 86, 128, 69, 56, 1, 201, 201, 7, 78, 96, 150, 223, 134, 218, 102, 56, 170, 45, 175, 98, 146, 19, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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