Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11c4f1eb65052657f4c7430e8bdddde782cf4fc11e495df08b1e94da10652e7a

Tx prefix hash: dd12a772d1279113ef0155faa1413ad937cec4681b535809e387c4ea019c1245
Tx public key: c1d486d816a2b1a0ff7149708ab1e1d51778f4ce9d3266aec7bd9b183472e04b
Timestamp: 1703622942 Timestamp [UCT]: 2023-12-26 20:35:42 Age [y:d:h:m:s]: 01:092:22:52:15
Block: 921782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327544 RingCT/type: yes/0
Extra: 01c1d486d816a2b1a0ff7149708ab1e1d51778f4ce9d3266aec7bd9b183472e04b021100000003ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8527f5e9a6c3c1026595992d52ce7ad8672747bfb4f6064c0b065aae0b6ede46 0.600000000000 1379476 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": 921792, "vin": [ { "gen": { "height": 921782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8527f5e9a6c3c1026595992d52ce7ad8672747bfb4f6064c0b065aae0b6ede46" } } ], "extra": [ 1, 193, 212, 134, 216, 22, 162, 177, 160, 255, 113, 73, 112, 138, 177, 225, 213, 23, 120, 244, 206, 157, 50, 102, 174, 199, 189, 155, 24, 52, 114, 224, 75, 2, 17, 0, 0, 0, 3, 173, 86, 148, 172, 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