Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f9069c0c3c3f926b0e767f7fdaa67a6cfc3726a7d80670454848f24863252b9

Tx prefix hash: ce047c565cd0add33f520b42ec2124aa0783535b5d59024332c3b1dbfbad3246
Tx public key: bb175a2316f04b33090bd183ffc0eec2e505a9ea6a5e12ab117af15f079f9cd4
Timestamp: 1734864788 Timestamp [UCT]: 2024-12-22 10:53:08 Age [y:d:h:m:s]: 00:132:09:01:19
Block: 1180705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94382 RingCT/type: yes/0
Extra: 01bb175a2316f04b33090bd183ffc0eec2e505a9ea6a5e12ab117af15f079f9cd40211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce22b8507379b303cbbc7bea9a4133fd6fbc88e75dfe55b6090bced79fa92d93 0.600000000000 1667118 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": 1180715, "vin": [ { "gen": { "height": 1180705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce22b8507379b303cbbc7bea9a4133fd6fbc88e75dfe55b6090bced79fa92d93" } } ], "extra": [ 1, 187, 23, 90, 35, 22, 240, 75, 51, 9, 11, 209, 131, 255, 192, 238, 194, 229, 5, 169, 234, 106, 94, 18, 171, 17, 122, 241, 95, 7, 159, 156, 212, 2, 17, 0, 0, 0, 7, 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