Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eeb68c247a73cf29f6a280458f0a6ea4f47d74892f83b0b100cda89f19582c13

Tx prefix hash: 54c2593f70f6adfcdcfd5281c798be206dc6fdc8b109ccc1c32ac8ffcea1f061
Tx public key: fc7b7c019b5f64dff2f1a329a4dad43620278edf3608ebdb8e8f61bb7963d64a
Timestamp: 1703969651 Timestamp [UCT]: 2023-12-30 20:54:11 Age [y:d:h:m:s]: 01:118:15:27:41
Block: 924642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345939 RingCT/type: yes/0
Extra: 01fc7b7c019b5f64dff2f1a329a4dad43620278edf3608ebdb8e8f61bb7963d64a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80cd557c0912598e1d073872891e7a31ad410754472aaccbe03f2bc149a561dd 0.600000000000 1382398 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": 924652, "vin": [ { "gen": { "height": 924642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80cd557c0912598e1d073872891e7a31ad410754472aaccbe03f2bc149a561dd" } } ], "extra": [ 1, 252, 123, 124, 1, 155, 95, 100, 223, 242, 241, 163, 41, 164, 218, 212, 54, 32, 39, 142, 223, 54, 8, 235, 219, 142, 143, 97, 187, 121, 99, 214, 74, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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