Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9449cac4d4b2e1eeecc3cfdad52f92cac90ee2ef1c6ff7af15f03a1c357950c

Tx prefix hash: b271d981e8863146c11860bac1589d81cc34e27f17a3bef34889cc1ab21df1ab
Tx public key: 599ae5617f31f670b513f6e885432b46e71d3a6b633667c4ba7bed4d9ea21189
Timestamp: 1717950415 Timestamp [UCT]: 2024-06-09 16:26:55 Age [y:d:h:m:s]: 01:007:20:03:35
Block: 1040572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266383 RingCT/type: yes/0
Extra: 01599ae5617f31f670b513f6e885432b46e71d3a6b633667c4ba7bed4d9ea211890211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e1f59b6bc1b3350260ee8be7304b320d3818de402a1b78b8d68a92aed160e41 0.600000000000 1509229 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": 1040582, "vin": [ { "gen": { "height": 1040572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e1f59b6bc1b3350260ee8be7304b320d3818de402a1b78b8d68a92aed160e41" } } ], "extra": [ 1, 89, 154, 229, 97, 127, 49, 246, 112, 181, 19, 246, 232, 133, 67, 43, 70, 231, 29, 58, 107, 99, 54, 103, 196, 186, 123, 237, 77, 158, 162, 17, 137, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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