Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fc054ee8b48cf6caff00e4734c7280a352b320b958b9e0dc1efd8c2a2132244

Tx prefix hash: de04ba1acdd7faa6f1346a59b36aaf7638f745dea14e9853e9601fe86fa8299b
Tx public key: a51b8d1a3b7a15a38ccfbd58521328999a8597a112d7117d239e9097d4daf642
Timestamp: 1712542257 Timestamp [UCT]: 2024-04-08 02:10:57 Age [y:d:h:m:s]: 01:276:03:49:05
Block: 995692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456158 RingCT/type: yes/0
Extra: 01a51b8d1a3b7a15a38ccfbd58521328999a8597a112d7117d239e9097d4daf64202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e309d4370343ca07d2a836cf2cdf523725a021c04bfaeaa36b072dd1918780e2 0.600000000000 1456106 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": 995702, "vin": [ { "gen": { "height": 995692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e309d4370343ca07d2a836cf2cdf523725a021c04bfaeaa36b072dd1918780e2" } } ], "extra": [ 1, 165, 27, 141, 26, 59, 122, 21, 163, 140, 207, 189, 88, 82, 19, 40, 153, 154, 133, 151, 161, 18, 215, 17, 125, 35, 158, 144, 151, 212, 218, 246, 66, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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