Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5f62d9abd847d27c32f98bcea8f3ac35452340b373acd6c55f4791eeb46157a

Tx prefix hash: 93bddca937d34b9cef833c77b3783b4099863b84ca118bbcae8492c49ba37a7a
Tx public key: bb08d162b87b554ae936003930033a9b76c48850bf507540926f11a4f96dc282
Timestamp: 1581824227 Timestamp [UCT]: 2020-02-16 03:37:07 Age [y:d:h:m:s]: 04:276:18:56:00
Block: 66012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1089973 RingCT/type: yes/0
Extra: 01bb08d162b87b554ae936003930033a9b76c48850bf507540926f11a4f96dc28202110000000412c4732d000000000000000000

1 output(s) for total of 370.916070872000 dcy

stealth address amount amount idx
00: 4167195fd4bc0e15d197f90a6818c50f34c6325a94a271b82c286c3d4a590f2d 370.916070872000 121653 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": 66022, "vin": [ { "gen": { "height": 66012 } } ], "vout": [ { "amount": 370916070872, "target": { "key": "4167195fd4bc0e15d197f90a6818c50f34c6325a94a271b82c286c3d4a590f2d" } } ], "extra": [ 1, 187, 8, 209, 98, 184, 123, 85, 74, 233, 54, 0, 57, 48, 3, 58, 155, 118, 196, 136, 80, 191, 80, 117, 64, 146, 111, 17, 164, 249, 109, 194, 130, 2, 17, 0, 0, 0, 4, 18, 196, 115, 45, 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