Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1307094dfa5cf189d8c6ab9a435ac5e63026c16a1b42aa2cf4b3c8e9094d1da

Tx prefix hash: f46fc6e54a3b1faed28b57708d9ce097224fddf178f9ae13b88ea0beaec943a2
Tx public key: 0fa53edfa20fc4e03256058eab343ce624391b9ed0529591050096a5fdf4820e
Timestamp: 1673871133 Timestamp [UCT]: 2023-01-16 12:12:13 Age [y:d:h:m:s]: 02:107:12:21:37
Block: 675981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 598529 RingCT/type: yes/0
Extra: 010fa53edfa20fc4e03256058eab343ce624391b9ed0529591050096a5fdf4820e0211000000018b7b6602000000000000000000

1 output(s) for total of 3.533412023000 dcy

stealth address amount amount idx
00: 56834073305f11f5a83e767d33fccc3986eb8f72b83a7d3597f0d250aa92a9c8 3.533412023000 1117676 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": 675991, "vin": [ { "gen": { "height": 675981 } } ], "vout": [ { "amount": 3533412023, "target": { "key": "56834073305f11f5a83e767d33fccc3986eb8f72b83a7d3597f0d250aa92a9c8" } } ], "extra": [ 1, 15, 165, 62, 223, 162, 15, 196, 224, 50, 86, 5, 142, 171, 52, 60, 230, 36, 57, 27, 158, 208, 82, 149, 145, 5, 0, 150, 165, 253, 244, 130, 14, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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