Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c771814026eeb022bd8013dac1bb692f6c93c0f32c0a8739705bd164c006a9ef

Tx prefix hash: 29befc66eb05c47f966bd5e76d472bcf83f91e5a2f83e49315751cef4c254a6f
Tx public key: 5d5849333d536a96241256cfd4c073ac70305f69ab6f3b39b66d85a6d0cf9cb9
Timestamp: 1750838299 Timestamp [UCT]: 2025-06-25 07:58:19 Age [y:d:h:m:s]: 00:144:02:44:14
Block: 1312386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100936 RingCT/type: yes/0
Extra: 015d5849333d536a96241256cfd4c073ac70305f69ab6f3b39b66d85a6d0cf9cb9021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d35e21dd85b2b9cbecf7d8659353b566ea69f536b8684ddd87ffe5dead93621f 0.600000000000 1800019 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": 1312396, "vin": [ { "gen": { "height": 1312386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d35e21dd85b2b9cbecf7d8659353b566ea69f536b8684ddd87ffe5dead93621f" } } ], "extra": [ 1, 93, 88, 73, 51, 61, 83, 106, 150, 36, 18, 86, 207, 212, 192, 115, 172, 112, 48, 95, 105, 171, 111, 59, 57, 182, 109, 133, 166, 208, 207, 156, 185, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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