Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 862734cffd91f19f6ac1c6859bea8373178f1f0b32f48ae42654a45f452fab74

Tx prefix hash: b9acb4171612af94d42b1e8a1c989cc0f7561827bb980e8aa0c8da27c9727842
Tx public key: 8db5991e82c700fa88888574a5d7cbcfdbb26f30dc97e544dd4d59d54fb08a4e
Timestamp: 1740101500 Timestamp [UCT]: 2025-02-21 01:31:40 Age [y:d:h:m:s]: 00:346:07:38:42
Block: 1223742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245202 RingCT/type: yes/0
Extra: 018db5991e82c700fa88888574a5d7cbcfdbb26f30dc97e544dd4d59d54fb08a4e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62eaec7e715c6d1b05ea7832439fa531b0308a82fad14354a109b77c249cdb2f 0.600000000000 1710599 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": 1223752, "vin": [ { "gen": { "height": 1223742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62eaec7e715c6d1b05ea7832439fa531b0308a82fad14354a109b77c249cdb2f" } } ], "extra": [ 1, 141, 181, 153, 30, 130, 199, 0, 250, 136, 136, 133, 116, 165, 215, 203, 207, 219, 178, 111, 48, 220, 151, 229, 68, 221, 77, 89, 213, 79, 176, 138, 78, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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