Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32bb00d24ba99e24646c35c06a38f617ea8746af9a0c23def7fb5b5267e004d5

Tx prefix hash: a49e80d4fa05f26c5822d4c40b6340090bb0681e3c961d3aeb054074bf21cff0
Tx public key: dbf457386c68204b5e12700a00deb78758d2ef4ad2b0c9eeb9fc80f8d1b76942
Timestamp: 1702440103 Timestamp [UCT]: 2023-12-13 04:01:43 Age [y:d:h:m:s]: 01:155:03:22:19
Block: 911993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372021 RingCT/type: yes/0
Extra: 01dbf457386c68204b5e12700a00deb78758d2ef4ad2b0c9eeb9fc80f8d1b7694202110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e27bdf8a01d0bd8cc7b077c3224cf83659f3987a713d25c3b9d6d815ceecebf7 0.600000000000 1369211 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": 912003, "vin": [ { "gen": { "height": 911993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e27bdf8a01d0bd8cc7b077c3224cf83659f3987a713d25c3b9d6d815ceecebf7" } } ], "extra": [ 1, 219, 244, 87, 56, 108, 104, 32, 75, 94, 18, 112, 10, 0, 222, 183, 135, 88, 210, 239, 74, 210, 176, 201, 238, 185, 252, 128, 248, 209, 183, 105, 66, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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