Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d66faf697fe6444b984238f1eb904b15d727c09e30bd2146c1b5945d34c952b

Tx prefix hash: 8bd1c97caa2ebc66b5fc0d3847154c00a05c5c2e724f2c81a647db6e900b42ea
Tx public key: 9aa4e76033e11e3431dd4a1f4e1ee8e516caf909af3b1df1a56ee77512734310
Timestamp: 1735256284 Timestamp [UCT]: 2024-12-26 23:38:04 Age [y:d:h:m:s]: 00:088:17:39:58
Block: 1183901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63213 RingCT/type: yes/0
Extra: 019aa4e76033e11e3431dd4a1f4e1ee8e516caf909af3b1df1a56ee77512734310021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b98ce56ea974fd44e7ca431f3ac3d6226cd9a60cd8b0a072bee8004e2ced71fb 0.600000000000 1670350 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": 1183911, "vin": [ { "gen": { "height": 1183901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b98ce56ea974fd44e7ca431f3ac3d6226cd9a60cd8b0a072bee8004e2ced71fb" } } ], "extra": [ 1, 154, 164, 231, 96, 51, 225, 30, 52, 49, 221, 74, 31, 78, 30, 232, 229, 22, 202, 249, 9, 175, 59, 29, 241, 165, 110, 231, 117, 18, 115, 67, 16, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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