Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed3b4b30d296e7235f748cd6f2a75fd2149a9b5cb3309b49b8ba5e3fb2fad20e

Tx prefix hash: e601fce4c23482eaf59698629fc955de76b2b618d8f51e6933be337328bb24ea
Tx public key: 3357d764f801fd201c5dfca70046d486c938599f1e4ea243ea63b8e13bd94a77
Timestamp: 1706300748 Timestamp [UCT]: 2024-01-26 20:25:48 Age [y:d:h:m:s]: 01:278:17:17:11
Block: 943948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458014 RingCT/type: yes/0
Extra: 013357d764f801fd201c5dfca70046d486c938599f1e4ea243ea63b8e13bd94a770211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a9a77dc42a55d43c4fc7396da0589b8b8bb68537349dc2eaf1e2a7f1dacbc70 0.600000000000 1402174 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": 943958, "vin": [ { "gen": { "height": 943948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a9a77dc42a55d43c4fc7396da0589b8b8bb68537349dc2eaf1e2a7f1dacbc70" } } ], "extra": [ 1, 51, 87, 215, 100, 248, 1, 253, 32, 28, 93, 252, 167, 0, 70, 212, 134, 201, 56, 89, 159, 30, 78, 162, 67, 234, 99, 184, 225, 59, 217, 74, 119, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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