Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6df76ea247d7c94df4836ce21072b5705a3362a9eccc78a12ab1db4d8425f807

Tx prefix hash: c879448f14f75a5785797c2e64033832e23e7f7c8c5d62adf2d660693dba7c8a
Tx public key: de70f72bd034bce4f7a9daa05acd41f5285fa1d0458610317b0d30c1e8044673
Timestamp: 1712787897 Timestamp [UCT]: 2024-04-10 22:24:57 Age [y:d:h:m:s]: 01:073:05:55:30
Block: 997744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313157 RingCT/type: yes/0
Extra: 01de70f72bd034bce4f7a9daa05acd41f5285fa1d0458610317b0d30c1e80446730211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0832a67f828c56d12ff61de70c93ef4b4cc5df436e25152a5b80044e69d87252 0.600000000000 1458178 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": 997754, "vin": [ { "gen": { "height": 997744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0832a67f828c56d12ff61de70c93ef4b4cc5df436e25152a5b80044e69d87252" } } ], "extra": [ 1, 222, 112, 247, 43, 208, 52, 188, 228, 247, 169, 218, 160, 90, 205, 65, 245, 40, 95, 161, 208, 69, 134, 16, 49, 123, 13, 48, 193, 232, 4, 70, 115, 2, 17, 0, 0, 0, 6, 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