Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea5552264f98e453419d5f72610615e4bba9c5edd07ecd441ee3e7f6462df96f

Tx prefix hash: f7d7f9893e27047452b68663bb2a015856d23a99edb53b3c693de1950b918430
Tx public key: 8dbaa9db70b4ca0531b029b5b54ddfc9d838de976823a2f1394b876611d1b1e5
Timestamp: 1710317401 Timestamp [UCT]: 2024-03-13 08:10:01 Age [y:d:h:m:s]: 01:054:14:47:01
Block: 977290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300037 RingCT/type: yes/0
Extra: 018dbaa9db70b4ca0531b029b5b54ddfc9d838de976823a2f1394b876611d1b1e502110000001052d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0ccbdd7d5424698ce1e7afabdf9e2bf854df091b43b444956f3c1eaf57f2f64 0.600000000000 1437291 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": 977300, "vin": [ { "gen": { "height": 977290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0ccbdd7d5424698ce1e7afabdf9e2bf854df091b43b444956f3c1eaf57f2f64" } } ], "extra": [ 1, 141, 186, 169, 219, 112, 180, 202, 5, 49, 176, 41, 181, 181, 77, 223, 201, 216, 56, 222, 151, 104, 35, 162, 241, 57, 75, 135, 102, 17, 209, 177, 229, 2, 17, 0, 0, 0, 16, 82, 212, 126, 148, 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