Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d6d9873e11c5b6a79047da0f82cc1d7ac29e21f4da1130ecc48ce7441b110ca

Tx prefix hash: e719c99de6121f999371eaf6514bf4e59dd86debdcb9aab547f3c99f86cd1522
Tx public key: 9d3da7cddc8a7a1201a864424ca055f84896ed63ecb58e3cb612b76de4517d46
Timestamp: 1738264671 Timestamp [UCT]: 2025-01-30 19:17:51 Age [y:d:h:m:s]: 00:295:05:08:50
Block: 1208559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208748 RingCT/type: yes/0
Extra: 019d3da7cddc8a7a1201a864424ca055f84896ed63ecb58e3cb612b76de4517d46021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc46a5b167a532c5be0c24bab7d80a1a0cfebc57c4f50bb1586225bac23f283b 0.600000000000 1695292 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": 1208569, "vin": [ { "gen": { "height": 1208559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc46a5b167a532c5be0c24bab7d80a1a0cfebc57c4f50bb1586225bac23f283b" } } ], "extra": [ 1, 157, 61, 167, 205, 220, 138, 122, 18, 1, 168, 100, 66, 76, 160, 85, 248, 72, 150, 237, 99, 236, 181, 142, 60, 182, 18, 183, 109, 228, 81, 125, 70, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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