Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e0b7e87ac61b62077a6f1167248c11034f90dddddbc5f2ff572e41db4fbdefb

Tx prefix hash: e1dddd5596b3364b5ccd42f8284b8a0553562c37305e0ff9aa10085589e2f130
Tx public key: 509ec29325fc0ff0a5b452872fcdea9fa37be3511f8f71786fce74b295c04f7a
Timestamp: 1724757767 Timestamp [UCT]: 2024-08-27 11:22:47 Age [y:d:h:m:s]: 01:074:04:45:31
Block: 1096994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311481 RingCT/type: yes/0
Extra: 01509ec29325fc0ff0a5b452872fcdea9fa37be3511f8f71786fce74b295c04f7a021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e66f2f93f4c80e766b34b51c7de44516bac42ccee44f785f0d4461db812c4b8b 0.600000000000 1572253 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": 1097004, "vin": [ { "gen": { "height": 1096994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e66f2f93f4c80e766b34b51c7de44516bac42ccee44f785f0d4461db812c4b8b" } } ], "extra": [ 1, 80, 158, 194, 147, 37, 252, 15, 240, 165, 180, 82, 135, 47, 205, 234, 159, 163, 123, 227, 81, 31, 143, 113, 120, 111, 206, 116, 178, 149, 192, 79, 122, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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