Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8867834a2b731f21ffc775621ed9400cd4c63f95b1f9d0ed8dbd14979543e09

Tx prefix hash: 99c8bb283ac6b074eec331257603a176cad706e9dd979f3e5b160eeaadf5fcde
Tx public key: 283dab9bb221b6c2c78a1e69af03920225abe163dd49a2e5ceafce99f14bdc08
Timestamp: 1581089733 Timestamp [UCT]: 2020-02-07 15:35:33 Age [y:d:h:m:s]: 04:333:12:33:43
Block: 60567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129926 RingCT/type: yes/0
Extra: 01283dab9bb221b6c2c78a1e69af03920225abe163dd49a2e5ceafce99f14bdc0802110000000356c366d3000000000000000000

1 output(s) for total of 386.649278353000 dcy

stealth address amount amount idx
00: e775ecfe80f7a1423ee07cb419104f917cb87da650f57df8b0e80b613ba3c3ee 386.649278353000 111580 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": 60577, "vin": [ { "gen": { "height": 60567 } } ], "vout": [ { "amount": 386649278353, "target": { "key": "e775ecfe80f7a1423ee07cb419104f917cb87da650f57df8b0e80b613ba3c3ee" } } ], "extra": [ 1, 40, 61, 171, 155, 178, 33, 182, 194, 199, 138, 30, 105, 175, 3, 146, 2, 37, 171, 225, 99, 221, 73, 162, 229, 206, 175, 206, 153, 241, 75, 220, 8, 2, 17, 0, 0, 0, 3, 86, 195, 102, 211, 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