Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dab39b472513989dd7904bca11d968e8dd472fe81dc827b523cd6ee1ab334a36

Tx prefix hash: 4d97ef0dfc7dbdefc98741aaad8f6ad88e813762816b6c138cf254ded394b084
Tx public key: e782ffa7274253bcc7b0ecd9b52bac72385a3df3fd0eb02b6ed26f0e939bb6b7
Timestamp: 1698491553 Timestamp [UCT]: 2023-10-28 11:12:33 Age [y:d:h:m:s]: 01:085:05:41:08
Block: 879469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322072 RingCT/type: yes/0
Extra: 01e782ffa7274253bcc7b0ecd9b52bac72385a3df3fd0eb02b6ed26f0e939bb6b70211000000044b8f5122000000000000000000

1 output(s) for total of 0.748090486000 dcy

stealth address amount amount idx
00: f398e00c1e5c9f6865169130e1d126666c31c6c521c2670868d1c03715f91a69 0.748090486000 1334993 of 0

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": 879479, "vin": [ { "gen": { "height": 879469 } } ], "vout": [ { "amount": 748090486, "target": { "key": "f398e00c1e5c9f6865169130e1d126666c31c6c521c2670868d1c03715f91a69" } } ], "extra": [ 1, 231, 130, 255, 167, 39, 66, 83, 188, 199, 176, 236, 217, 181, 43, 172, 114, 56, 90, 61, 243, 253, 14, 176, 43, 110, 210, 111, 14, 147, 155, 182, 183, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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