Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23e7a0ea76bc122c99f39318b255d2134bb8fb11c5a1b3fa286e7c03dc7c882b

Tx prefix hash: 7ecddb9daff91f22577bfb4753b17d95247dda34d41e1f2bfdbd867bba8f4c0b
Tx public key: 6be09465c96a78c3b79ab5a3cdc86e5943eb2bfa240068caa100f6cd38dd8b5b
Timestamp: 1724690022 Timestamp [UCT]: 2024-08-26 16:33:42 Age [y:d:h:m:s]: 01:075:16:17:20
Block: 1096430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312541 RingCT/type: yes/0
Extra: 016be09465c96a78c3b79ab5a3cdc86e5943eb2bfa240068caa100f6cd38dd8b5b02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1444b2b11e5e499261075bbea65f1f5c1c281b94f787a243950593a3cf74fdd8 0.600000000000 1571619 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": 1096440, "vin": [ { "gen": { "height": 1096430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1444b2b11e5e499261075bbea65f1f5c1c281b94f787a243950593a3cf74fdd8" } } ], "extra": [ 1, 107, 224, 148, 101, 201, 106, 120, 195, 183, 154, 181, 163, 205, 200, 110, 89, 67, 235, 43, 250, 36, 0, 104, 202, 161, 0, 246, 205, 56, 221, 139, 91, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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