Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bed409582c60abf4d13feb0a383d66adf157d4d7161df470067d4c038c2999c

Tx prefix hash: 5aab0617dcee713bbb4b5c88c59f6c0e39ba6fcb176e06daa8e74cd1b0d73211
Tx public key: 68914650e48719e5d21c1daf3bce45d336462924a9928db533e28dd89e252d59
Timestamp: 1577712989 Timestamp [UCT]: 2019-12-30 13:36:29 Age [y:d:h:m:s]: 05:000:10:10:08
Block: 35062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150284 RingCT/type: yes/0
Extra: 0168914650e48719e5d21c1daf3bce45d336462924a9928db533e28dd89e252d5902110000000a4ac5aa02000000000000000000

1 output(s) for total of 469.705768622000 dcy

stealth address amount amount idx
00: 0c7635b9183fccdb62ff453c1393c2c1f54184ceff01ddeba3eabaefcb3276e7 469.705768622000 59055 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": 35072, "vin": [ { "gen": { "height": 35062 } } ], "vout": [ { "amount": 469705768622, "target": { "key": "0c7635b9183fccdb62ff453c1393c2c1f54184ceff01ddeba3eabaefcb3276e7" } } ], "extra": [ 1, 104, 145, 70, 80, 228, 135, 25, 229, 210, 28, 29, 175, 59, 206, 69, 211, 54, 70, 41, 36, 169, 146, 141, 181, 51, 226, 141, 216, 158, 37, 45, 89, 2, 17, 0, 0, 0, 10, 74, 197, 170, 2, 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