Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbadcc3bdd312a38daae3af09176c5ef1d7c9f5e19adb527a6664a43c60ca2ff

Tx prefix hash: a4b5f519570a02344e1ad5331f228cda51ccf3f013c1d2bea2f4e832e833de0a
Tx public key: 1df3cf6e33f0a9da202ee6154ff695d3aae540ff95364bcaa4064045e0aa87dd
Timestamp: 1607763453 Timestamp [UCT]: 2020-12-12 08:57:33 Age [y:d:h:m:s]: 04:013:22:17:47
Block: 160507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1022213 RingCT/type: yes/0
Extra: 011df3cf6e33f0a9da202ee6154ff695d3aae540ff95364bcaa4064045e0aa87dd021100000aec57f0ba47000000000000000000

1 output(s) for total of 180.379425561000 dcy

stealth address amount amount idx
00: 2e31ccfba4d17aae2f5771cdbd5ad071cf140143508fbedfd38045ed1acc7477 180.379425561000 282889 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": 160517, "vin": [ { "gen": { "height": 160507 } } ], "vout": [ { "amount": 180379425561, "target": { "key": "2e31ccfba4d17aae2f5771cdbd5ad071cf140143508fbedfd38045ed1acc7477" } } ], "extra": [ 1, 29, 243, 207, 110, 51, 240, 169, 218, 32, 46, 230, 21, 79, 246, 149, 211, 170, 229, 64, 255, 149, 54, 75, 202, 164, 6, 64, 69, 224, 170, 135, 221, 2, 17, 0, 0, 10, 236, 87, 240, 186, 71, 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