Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33c193cebf01078ef755d0db4b5e65ab5d1f9759fcd847cfd860e66bbc43d855

Tx prefix hash: 59dcce8f03a91d0f050578ae41ecb1bbd582d08661272ff83f53ef29f4b71d02
Tx public key: 6e57e7c7f07052038686b5bbeb812a1e276c889c3ad41ed4dbfd1a2ad45a7bfd
Timestamp: 1729298404 Timestamp [UCT]: 2024-10-19 00:40:04 Age [y:d:h:m:s]: 00:245:01:03:52
Block: 1134643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174786 RingCT/type: yes/0
Extra: 016e57e7c7f07052038686b5bbeb812a1e276c889c3ad41ed4dbfd1a2ad45a7bfd0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a913de9430b3a09642b753bcdd87a57f980c835a611c50b51ffcce27c8b80989 0.600000000000 1617968 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": 1134653, "vin": [ { "gen": { "height": 1134643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a913de9430b3a09642b753bcdd87a57f980c835a611c50b51ffcce27c8b80989" } } ], "extra": [ 1, 110, 87, 231, 199, 240, 112, 82, 3, 134, 134, 181, 187, 235, 129, 42, 30, 39, 108, 136, 156, 58, 212, 30, 212, 219, 253, 26, 42, 212, 90, 123, 253, 2, 17, 0, 0, 0, 6, 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