Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0f1ca9ac0fca3e23fb2e89d3bce8f0168db7be59a0ab74a92a7c5c7618e8d6c

Tx prefix hash: 98efff65d52f7549b0c320216daa5bf59de8ffb1e305b256fd435be5d2f42c54
Tx public key: d3244e919692fe2e26c146117bcb982e7464bc2c5b39c1361227f3a2d966107c
Timestamp: 1700994512 Timestamp [UCT]: 2023-11-26 10:28:32 Age [y:d:h:m:s]: 01:140:06:40:24
Block: 899982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361436 RingCT/type: yes/0
Extra: 01d3244e919692fe2e26c146117bcb982e7464bc2c5b39c1361227f3a2d966107c02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.639714238000 dcy

stealth address amount amount idx
00: b32811fb2e2abd46d81c3f73b01f76a7b38277eb5f77447b424d841e1e06d2b2 0.639714238000 1356453 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": 899992, "vin": [ { "gen": { "height": 899982 } } ], "vout": [ { "amount": 639714238, "target": { "key": "b32811fb2e2abd46d81c3f73b01f76a7b38277eb5f77447b424d841e1e06d2b2" } } ], "extra": [ 1, 211, 36, 78, 145, 150, 146, 254, 46, 38, 193, 70, 17, 123, 203, 152, 46, 116, 100, 188, 44, 91, 57, 193, 54, 18, 39, 243, 162, 217, 102, 16, 124, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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