Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75f24505bdf2fc46de6ea4a7bca031c607a0f0f948fbd6cd59d4908a80d1512f

Tx prefix hash: a28ef43f2e1fe7596539059fc2cf14f9633061053332f703290cb57c1c86bb01
Tx public key: 85c702fd2d7702ebfaa53b79c804f5ba6b6ddc635c2c35608a14ad492b54bdb4
Timestamp: 1710743726 Timestamp [UCT]: 2024-03-18 06:35:26 Age [y:d:h:m:s]: 01:044:17:07:26
Block: 980836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292935 RingCT/type: yes/0
Extra: 0185c702fd2d7702ebfaa53b79c804f5ba6b6ddc635c2c35608a14ad492b54bdb402110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72567aa5124d051726e2dd7f4045fe9fc61928b832f3ef576d2308e2a98e9dc1 0.600000000000 1440919 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": 980846, "vin": [ { "gen": { "height": 980836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72567aa5124d051726e2dd7f4045fe9fc61928b832f3ef576d2308e2a98e9dc1" } } ], "extra": [ 1, 133, 199, 2, 253, 45, 119, 2, 235, 250, 165, 59, 121, 200, 4, 245, 186, 107, 109, 220, 99, 92, 44, 53, 96, 138, 20, 173, 73, 43, 84, 189, 180, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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