Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a8819b393642c9d750cd4767ead306844306f78f9c25d2ac0f7e38ba84b842e

Tx prefix hash: 3f034f95965d4eedf03fff448128e71379743c30fca26166da0b5444c75afd0a
Tx public key: b8e6f9e983616c61379ca16ec1419e2848ba4410b8c81506c3c00db418c893f6
Timestamp: 1738123151 Timestamp [UCT]: 2025-01-29 03:59:11 Age [y:d:h:m:s]: 00:144:17:26:27
Block: 1207393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103305 RingCT/type: yes/0
Extra: 01b8e6f9e983616c61379ca16ec1419e2848ba4410b8c81506c3c00db418c893f60211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78c042bec4c4334247f6c69d8245a2f7e3e9950b3fdb8ad784ccb07b9ed91ad3 0.600000000000 1694116 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": 1207403, "vin": [ { "gen": { "height": 1207393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78c042bec4c4334247f6c69d8245a2f7e3e9950b3fdb8ad784ccb07b9ed91ad3" } } ], "extra": [ 1, 184, 230, 249, 233, 131, 97, 108, 97, 55, 156, 161, 110, 193, 65, 158, 40, 72, 186, 68, 16, 184, 200, 21, 6, 195, 192, 13, 180, 24, 200, 147, 246, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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