Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4a1e3828991e4511a9eb7bad34eed5024d78c23fb5ef2625d136f8017a89c65

Tx prefix hash: a260f27358277d605bb9a8169948d8b4a1175602aad4439de6fe6413ac64df49
Tx public key: 0e7e46208f0c177b7c43075eed6d35e5e6fc809f7674f4484223aa3cb3283e21
Timestamp: 1710678997 Timestamp [UCT]: 2024-03-17 12:36:37 Age [y:d:h:m:s]: 01:018:02:17:14
Block: 980303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273898 RingCT/type: yes/0
Extra: 010e7e46208f0c177b7c43075eed6d35e5e6fc809f7674f4484223aa3cb3283e2102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36e3e89e8df15ad3c9d16dadd674e220bc550173a51816e49eee807694e7087c 0.600000000000 1440368 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": 980313, "vin": [ { "gen": { "height": 980303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36e3e89e8df15ad3c9d16dadd674e220bc550173a51816e49eee807694e7087c" } } ], "extra": [ 1, 14, 126, 70, 32, 143, 12, 23, 123, 124, 67, 7, 94, 237, 109, 53, 229, 230, 252, 128, 159, 118, 116, 244, 72, 66, 35, 170, 60, 179, 40, 62, 33, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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