Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e44cb01aeb2221213f82c2998f634669a79ee78cfcc81be74f7ebc842de7ec93

Tx prefix hash: 54a9df1c8047f416eed17baf836392caf49650fab256b176f95d61572dc21f89
Tx public key: 6a5105c919e5c24e493788b94c25702ae7d8d35c6b019fd0d32fcb6d8a101918
Timestamp: 1709259978 Timestamp [UCT]: 2024-03-01 02:26:18 Age [y:d:h:m:s]: 01:091:02:41:58
Block: 968527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326167 RingCT/type: yes/0
Extra: 016a5105c919e5c24e493788b94c25702ae7d8d35c6b019fd0d32fcb6d8a10191802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4f9359c974d0d14613730bb97cb1e674d34018ac43874e9e6c579ef88b48295 0.600000000000 1428342 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": 968537, "vin": [ { "gen": { "height": 968527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4f9359c974d0d14613730bb97cb1e674d34018ac43874e9e6c579ef88b48295" } } ], "extra": [ 1, 106, 81, 5, 201, 25, 229, 194, 78, 73, 55, 136, 185, 76, 37, 112, 42, 231, 216, 211, 92, 107, 1, 159, 208, 211, 47, 203, 109, 138, 16, 25, 24, 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