Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a67d76b52e861055d5556c5fdd5e314fc9dcd592bba32ce6f29e11074ed99a84

Tx prefix hash: 81be47824577fdd43882e0efda8978ea7bf9e1bb543852c658cb7cc630b13b1b
Tx public key: 31dcb6de33ccff639425ca678c6ea5eee3f541ed0df4645ad0e99ee70fdc3d60
Timestamp: 1729763819 Timestamp [UCT]: 2024-10-24 09:56:59 Age [y:d:h:m:s]: 01:095:04:16:10
Block: 1138466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326330 RingCT/type: yes/0
Extra: 0131dcb6de33ccff639425ca678c6ea5eee3f541ed0df4645ad0e99ee70fdc3d600211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b23594d80e05d2bae9a8de41a941876c83573422a70a21ac4c500551f9ed9aa 0.600000000000 1622143 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": 1138476, "vin": [ { "gen": { "height": 1138466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b23594d80e05d2bae9a8de41a941876c83573422a70a21ac4c500551f9ed9aa" } } ], "extra": [ 1, 49, 220, 182, 222, 51, 204, 255, 99, 148, 37, 202, 103, 140, 110, 165, 238, 227, 245, 65, 237, 13, 244, 100, 90, 208, 233, 158, 231, 15, 220, 61, 96, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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