Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89aad58440b3c7e563115efceea0941bbef39ef6d3082a2796c689f0ae8ddabb

Tx prefix hash: c04b8a681c91b0bb1da77fcff1e224793e8f41ae8c995036704c7cad959d475b
Tx public key: 93862d886906d03a9f88f91afdfc2046875ee52995ff92b5940c654f6a489c8c
Timestamp: 1729074211 Timestamp [UCT]: 2024-10-16 10:23:31 Age [y:d:h:m:s]: 00:242:22:26:30
Block: 1132799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173320 RingCT/type: yes/0
Extra: 0193862d886906d03a9f88f91afdfc2046875ee52995ff92b5940c654f6a489c8c0211000000083cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e655457c2612f0b3b82e8a846b0c1c4404e330db2b9a581d2d6d30ab8930e06b 0.600000000000 1615800 of 15

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": 1132809, "vin": [ { "gen": { "height": 1132799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e655457c2612f0b3b82e8a846b0c1c4404e330db2b9a581d2d6d30ab8930e06b" } } ], "extra": [ 1, 147, 134, 45, 136, 105, 6, 208, 58, 159, 136, 249, 26, 253, 252, 32, 70, 135, 94, 229, 41, 149, 255, 146, 181, 148, 12, 101, 79, 106, 72, 156, 140, 2, 17, 0, 0, 0, 8, 60, 208, 252, 6, 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