Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 967d8c7a695aebdd8571afea10694f612f89aecd148b8812d0aaac81a2348001

Tx prefix hash: ad00b4da39a44d60a9735f3bb8fee560b7b7ce3e1a3dd755ccf303894958ac68
Tx public key: dd2e26e45439b4bbd47e13cb73b4dac7e07ae02979e6e94aa753a3ca25e7877b
Timestamp: 1581949739 Timestamp [UCT]: 2020-02-17 14:28:59 Age [y:d:h:m:s]: 05:119:20:46:31
Block: 66877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1238618 RingCT/type: yes/0
Extra: 01dd2e26e45439b4bbd47e13cb73b4dac7e07ae02979e6e94aa753a3ca25e7877b02110000000156c366d3000000000000000000

1 output(s) for total of 368.476287743000 dcy

stealth address amount amount idx
00: e381829093e2f0374e0f58032c8d13f7dbae3acf0c4b6cd0c311f456e450eec7 368.476287743000 123106 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": 66887, "vin": [ { "gen": { "height": 66877 } } ], "vout": [ { "amount": 368476287743, "target": { "key": "e381829093e2f0374e0f58032c8d13f7dbae3acf0c4b6cd0c311f456e450eec7" } } ], "extra": [ 1, 221, 46, 38, 228, 84, 57, 180, 187, 212, 126, 19, 203, 115, 180, 218, 199, 224, 122, 224, 41, 121, 230, 233, 74, 167, 83, 163, 202, 37, 231, 135, 123, 2, 17, 0, 0, 0, 1, 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