Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ec4d526fae4999762d3afa08d4806e258b8f3e1e654483b8b31a10d97394ab9

Tx prefix hash: 3104a1802372ca9728e065c21266bc3d4f2e4d334ddb434f614f8c0138883e28
Tx public key: 039a240f725ee6a42e1d0c05c79d9d6a17dc6d4c0f75961c593dd4bbf65409fe
Timestamp: 1734087807 Timestamp [UCT]: 2024-12-13 11:03:27 Age [y:d:h:m:s]: 00:116:01:12:42
Block: 1174260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82706 RingCT/type: yes/0
Extra: 01039a240f725ee6a42e1d0c05c79d9d6a17dc6d4c0f75961c593dd4bbf65409fe02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0308e09a1db20802b7d9389e59f4f6e7a1fcbf1ed68cd32c385c11b51b914007 0.600000000000 1660391 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": 1174270, "vin": [ { "gen": { "height": 1174260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0308e09a1db20802b7d9389e59f4f6e7a1fcbf1ed68cd32c385c11b51b914007" } } ], "extra": [ 1, 3, 154, 36, 15, 114, 94, 230, 164, 46, 29, 12, 5, 199, 157, 157, 106, 23, 220, 109, 76, 15, 117, 150, 28, 89, 61, 212, 187, 246, 84, 9, 254, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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