Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec80d52413caf299388e4e8f5e8893d76c79fc05d2b22f5c3c97e1f037a057d9

Tx prefix hash: 16eb9b679d56f23d5f807acecf168da6eb6d0a219e0d6c0c1939152be495143a
Tx public key: 326a3aa2e68c7dc1fed2638b47b3f1d89832a17bbac81ae3ad4dff5a56d8c2ca
Timestamp: 1685485472 Timestamp [UCT]: 2023-05-30 22:24:32 Age [y:d:h:m:s]: 01:148:09:51:43
Block: 771666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367461 RingCT/type: yes/0
Extra: 01326a3aa2e68c7dc1fed2638b47b3f1d89832a17bbac81ae3ad4dff5a56d8c2ca021100000003faf35c9c000000000000000000

1 output(s) for total of 1.702748003000 dcy

stealth address amount amount idx
00: 1a12b1482132f587709712b9f8fe168b6bda09bf63893809ce98f7832938371e 1.702748003000 1221041 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": 771676, "vin": [ { "gen": { "height": 771666 } } ], "vout": [ { "amount": 1702748003, "target": { "key": "1a12b1482132f587709712b9f8fe168b6bda09bf63893809ce98f7832938371e" } } ], "extra": [ 1, 50, 106, 58, 162, 230, 140, 125, 193, 254, 210, 99, 139, 71, 179, 241, 216, 152, 50, 161, 123, 186, 200, 26, 227, 173, 77, 255, 90, 86, 216, 194, 202, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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