Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89e626066fe2f1ed9b0680233e88f68a09408d65862bbf385e3b0955d52b336c

Tx prefix hash: df5680d48a819abbcac5408a38d94d939123c40a5e68d320f479b6010b462c95
Tx public key: 419b53ad0d977e28fe630adbf2ed9ee3ede9f7a5a5b6e422868c486af65a1526
Timestamp: 1574490345 Timestamp [UCT]: 2019-11-23 06:25:45 Age [y:d:h:m:s]: 05:079:13:21:34
Block: 15130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1199878 RingCT/type: yes/0
Extra: 01419b53ad0d977e28fe630adbf2ed9ee3ede9f7a5a5b6e422868c486af65a15260211000000170b4dd45a000000000000000000

1 output(s) for total of 546.850877330000 dcy

stealth address amount amount idx
00: 5ee03769e1ed328ab9c330f21590e784eb3e10e23a33461a945e9415e6c9cc60 546.850877330000 20016 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": 15140, "vin": [ { "gen": { "height": 15130 } } ], "vout": [ { "amount": 546850877330, "target": { "key": "5ee03769e1ed328ab9c330f21590e784eb3e10e23a33461a945e9415e6c9cc60" } } ], "extra": [ 1, 65, 155, 83, 173, 13, 151, 126, 40, 254, 99, 10, 219, 242, 237, 158, 227, 237, 233, 247, 165, 165, 182, 228, 34, 134, 140, 72, 106, 246, 90, 21, 38, 2, 17, 0, 0, 0, 23, 11, 77, 212, 90, 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