Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b951ed23e2f0a831e2faad939f36eba4eb9d0f1d2819adef4089f0b0a0d8130

Tx prefix hash: 571132888e6cb7f6f89299299ae3deedbee61ae3f31f38320c81a5036a86c77e
Tx public key: d4d24edf002c6e5b30e55f65b7c806982d6355e118f18d2eed3976b2528b8853
Timestamp: 1694095019 Timestamp [UCT]: 2023-09-07 13:56:59 Age [y:d:h:m:s]: 01:178:03:13:38
Block: 842977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388397 RingCT/type: yes/0
Extra: 01d4d24edf002c6e5b30e55f65b7c806982d6355e118f18d2eed3976b2528b88530211000000114b8f5122000000000000000000

1 output(s) for total of 0.988251153000 dcy

stealth address amount amount idx
00: 0bc2a6e64ba24045c22d87c5c620a3cdcdacac1ffc7c336c2fc2963d063c6873 0.988251153000 1296159 of 0

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": 842987, "vin": [ { "gen": { "height": 842977 } } ], "vout": [ { "amount": 988251153, "target": { "key": "0bc2a6e64ba24045c22d87c5c620a3cdcdacac1ffc7c336c2fc2963d063c6873" } } ], "extra": [ 1, 212, 210, 78, 223, 0, 44, 110, 91, 48, 229, 95, 101, 183, 200, 6, 152, 45, 99, 85, 225, 24, 241, 141, 46, 237, 57, 118, 178, 82, 139, 136, 83, 2, 17, 0, 0, 0, 17, 75, 143, 81, 34, 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