Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9f65f7bbdfea05b3a5c600fef558db9f82b83d491311b0068a23309690e0d11

Tx prefix hash: 9812ba2e6ac0bd98af44adc6341b31aa6c1ffc7e876930a25bd6724cf844a8f6
Tx public key: d7f4c3f74be544bb2c3417112d97c8f5840258361f662d9283f1b0e21ce00679
Timestamp: 1582747267 Timestamp [UCT]: 2020-02-26 20:01:07 Age [y:d:h:m:s]: 04:274:00:28:15
Block: 72446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1089190 RingCT/type: yes/0
Extra: 01d7f4c3f74be544bb2c3417112d97c8f5840258361f662d9283f1b0e21ce006790211000000068a2ee0d9000000000000000000

1 output(s) for total of 353.148306801000 dcy

stealth address amount amount idx
00: e5ff742ccfb001cc1e1806e1d0c2e1792c5666476768960643dacb3da50ecdd2 353.148306801000 133842 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": 72456, "vin": [ { "gen": { "height": 72446 } } ], "vout": [ { "amount": 353148306801, "target": { "key": "e5ff742ccfb001cc1e1806e1d0c2e1792c5666476768960643dacb3da50ecdd2" } } ], "extra": [ 1, 215, 244, 195, 247, 75, 229, 68, 187, 44, 52, 23, 17, 45, 151, 200, 245, 132, 2, 88, 54, 31, 102, 45, 146, 131, 241, 176, 226, 28, 224, 6, 121, 2, 17, 0, 0, 0, 6, 138, 46, 224, 217, 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