Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66cc0c845fad967389fff7c5d3fab941d439f5eb322452489d6176e5f1712839

Tx prefix hash: 8fed7f41efbfeea01512e1114e8880baeee159a54435eab39f4636b7cbbb4b09
Tx public key: e7f39d35814eb7df12c933671a017d9142f5aba3753b6d45ff803362db5501d4
Timestamp: 1710322015 Timestamp [UCT]: 2024-03-13 09:26:55 Age [y:d:h:m:s]: 01:100:02:34:55
Block: 977330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332408 RingCT/type: yes/0
Extra: 01e7f39d35814eb7df12c933671a017d9142f5aba3753b6d45ff803362db5501d40211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6c7315739d17d356e8acf3d4438eb5e1d78c963adfc9d67df8f2bbd85629139 0.600000000000 1437333 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": 977340, "vin": [ { "gen": { "height": 977330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6c7315739d17d356e8acf3d4438eb5e1d78c963adfc9d67df8f2bbd85629139" } } ], "extra": [ 1, 231, 243, 157, 53, 129, 78, 183, 223, 18, 201, 51, 103, 26, 1, 125, 145, 66, 245, 171, 163, 117, 59, 109, 69, 255, 128, 51, 98, 219, 85, 1, 212, 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