Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe6b71ac1a945e339241a7da55db19010863b77131b4712134068e258f1c6b5e

Tx prefix hash: ef61d93feffcc102428f2263ec7ad661909fd63198b4479ce481a22cb8a1c6e1
Tx public key: 475ffcf30feb0f785a2c9d47fa94a9f038775e43c8bc5b14cccd5aab6b01963b
Timestamp: 1712841939 Timestamp [UCT]: 2024-04-11 13:25:39 Age [y:d:h:m:s]: 00:234:09:14:58
Block: 998188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167813 RingCT/type: yes/0
Extra: 01475ffcf30feb0f785a2c9d47fa94a9f038775e43c8bc5b14cccd5aab6b01963b0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c80ce1a5e2d98af48ca4cde57e98ce6afebb9e2d9fa70d11910a328e8f155db4 0.600000000000 1458632 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": 998198, "vin": [ { "gen": { "height": 998188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c80ce1a5e2d98af48ca4cde57e98ce6afebb9e2d9fa70d11910a328e8f155db4" } } ], "extra": [ 1, 71, 95, 252, 243, 15, 235, 15, 120, 90, 44, 157, 71, 250, 148, 169, 240, 56, 119, 94, 67, 200, 188, 91, 20, 204, 205, 90, 171, 107, 1, 150, 59, 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