Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf07b372419fee5c3ff3172f24c51a37efd23cf158db0dc08a3e3bfaded0a356

Tx prefix hash: 78dfa5aef79aa0bb2448a35dbb3455eb0045c4173446296d2676bbd6e05a0cb8
Tx public key: d9241685a24b8602b4c11e61eba2264923fcc2263cb9dc65eac9a0b84c32630c
Timestamp: 1698266720 Timestamp [UCT]: 2023-10-25 20:45:20 Age [y:d:h:m:s]: 01:151:06:05:56
Block: 877589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369090 RingCT/type: yes/0
Extra: 01d9241685a24b8602b4c11e61eba2264923fcc2263cb9dc65eac9a0b84c32630c0211000000014b8f5122000000000000000000

1 output(s) for total of 0.758897906000 dcy

stealth address amount amount idx
00: 7cd6dcb3d08e63b3a81c4aabe0b128e951fe4c5e25f288ceecb1a51fba51e9f2 0.758897906000 1332971 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": 877599, "vin": [ { "gen": { "height": 877589 } } ], "vout": [ { "amount": 758897906, "target": { "key": "7cd6dcb3d08e63b3a81c4aabe0b128e951fe4c5e25f288ceecb1a51fba51e9f2" } } ], "extra": [ 1, 217, 36, 22, 133, 162, 75, 134, 2, 180, 193, 30, 97, 235, 162, 38, 73, 35, 252, 194, 38, 60, 185, 220, 101, 234, 201, 160, 184, 76, 50, 99, 12, 2, 17, 0, 0, 0, 1, 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