Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd7c404f476607e17e84c06b531d4a8a0f09ed24250bcce6b536f7ffb3dfeab4

Tx prefix hash: 806287f514952336ba5608272551f8661d8879bf8fae39a7d1d5eb57a4082883
Tx public key: 9403bbb802ce2e6127f5c2267b4f77e9bca3faeeaa04296f2665577bca0a6a0c
Timestamp: 1708143972 Timestamp [UCT]: 2024-02-17 04:26:12 Age [y:d:h:m:s]: 01:040:07:30:34
Block: 959261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289840 RingCT/type: yes/0
Extra: 019403bbb802ce2e6127f5c2267b4f77e9bca3faeeaa04296f2665577bca0a6a0c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 401c46b8f67c1992a755d73a4d16475fb008dd4d03209aef81519ce31c51f137 0.600000000000 1418792 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": 959271, "vin": [ { "gen": { "height": 959261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "401c46b8f67c1992a755d73a4d16475fb008dd4d03209aef81519ce31c51f137" } } ], "extra": [ 1, 148, 3, 187, 184, 2, 206, 46, 97, 39, 245, 194, 38, 123, 79, 119, 233, 188, 163, 250, 238, 170, 4, 41, 111, 38, 101, 87, 123, 202, 10, 106, 12, 2, 17, 0, 0, 0, 1, 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