Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 519f46525728aa99b3b1f309c0d18659a101087f63ee2edbc34635582177c200

Tx prefix hash: ef366ec620e282170015f498ed1ece0d00138481282185e7aa13b28580e748c2
Tx public key: aea4948cb9dafa40487a73cb8cbf3be628ff88c457b8b5d2574e404605c170e8
Timestamp: 1713677270 Timestamp [UCT]: 2024-04-21 05:27:50 Age [y:d:h:m:s]: 00:309:23:30:23
Block: 1005132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221573 RingCT/type: yes/0
Extra: 01aea4948cb9dafa40487a73cb8cbf3be628ff88c457b8b5d2574e404605c170e802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b53e4b06fb68cec8d905ca8478f177e29d07a4b5f063661eb41d0d2079f39012 0.600000000000 1465712 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": 1005142, "vin": [ { "gen": { "height": 1005132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b53e4b06fb68cec8d905ca8478f177e29d07a4b5f063661eb41d0d2079f39012" } } ], "extra": [ 1, 174, 164, 148, 140, 185, 218, 250, 64, 72, 122, 115, 203, 140, 191, 59, 230, 40, 255, 136, 196, 87, 184, 181, 210, 87, 78, 64, 70, 5, 193, 112, 232, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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