Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e886530ca396cb708264ab87a08cc6386b7a7fe463cc455cb65576427522885c

Tx prefix hash: 9d7f720ce09bc5a561ce99af78d86c23a17fc206daf68e80d302a0d9a8927a2c
Tx public key: 3884c06f4a2be2e8a66b92c70c5d01edce4a7787f3e727725c61fcacc58c8ae8
Timestamp: 1726702679 Timestamp [UCT]: 2024-09-18 23:37:59 Age [y:d:h:m:s]: 00:202:04:57:55
Block: 1113127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144331 RingCT/type: yes/0
Extra: 013884c06f4a2be2e8a66b92c70c5d01edce4a7787f3e727725c61fcacc58c8ae8021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6da953524f793fb123bfcac055136338ae138a4ee037dc51bc51b96222affe9 0.600000000000 1592686 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": 1113137, "vin": [ { "gen": { "height": 1113127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6da953524f793fb123bfcac055136338ae138a4ee037dc51bc51b96222affe9" } } ], "extra": [ 1, 56, 132, 192, 111, 74, 43, 226, 232, 166, 107, 146, 199, 12, 93, 1, 237, 206, 74, 119, 135, 243, 231, 39, 114, 92, 97, 252, 172, 197, 140, 138, 232, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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