Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d7cca45689331648b4ffadeaecc5d6c8341526fe2e034ed43e10b915f09d5a4

Tx prefix hash: efb0473c54f159a4a445147c4e8827091fe0bc71c8cdfb9fc914524a7975aa18
Tx public key: 536eabd79558c384dea4b6d70b6fbc91d11172bffe746d5f070df6e4b517003c
Timestamp: 1702807703 Timestamp [UCT]: 2023-12-17 10:08:23 Age [y:d:h:m:s]: 01:122:19:55:49
Block: 915023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348929 RingCT/type: yes/0
Extra: 01536eabd79558c384dea4b6d70b6fbc91d11172bffe746d5f070df6e4b517003c021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8ff35b9735edfc7a7856107f737f2762178df5c9957dc1f2891344c18bacda6 0.600000000000 1372393 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": 915033, "vin": [ { "gen": { "height": 915023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8ff35b9735edfc7a7856107f737f2762178df5c9957dc1f2891344c18bacda6" } } ], "extra": [ 1, 83, 110, 171, 215, 149, 88, 195, 132, 222, 164, 182, 215, 11, 111, 188, 145, 209, 17, 114, 191, 254, 116, 109, 95, 7, 13, 246, 228, 181, 23, 0, 60, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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