Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02cb4fbb640175aedcc116e59d0af68bdca33888990644235b1f797298bcf5ff

Tx prefix hash: 2abf7bd5c82595c4d99c535f5f902a12194d2de606cba5a2802a749215c4bee8
Tx public key: b2879248ce52175a60f7dfb1fa83c9733c4cfbd1b8c5f27addf94a3e77bd4abf
Timestamp: 1694898090 Timestamp [UCT]: 2023-09-16 21:01:30 Age [y:d:h:m:s]: 01:243:17:17:50
Block: 849632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435308 RingCT/type: yes/0
Extra: 01b2879248ce52175a60f7dfb1fa83c9733c4cfbd1b8c5f27addf94a3e77bd4abf02110000000333af99f4000000000000000000

1 output(s) for total of 0.939326430000 dcy

stealth address amount amount idx
00: b5956db515a4e0260a326dc3a6ef84de83d96e60b158d27d4ae6e10a642c5694 0.939326430000 1303306 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": 849642, "vin": [ { "gen": { "height": 849632 } } ], "vout": [ { "amount": 939326430, "target": { "key": "b5956db515a4e0260a326dc3a6ef84de83d96e60b158d27d4ae6e10a642c5694" } } ], "extra": [ 1, 178, 135, 146, 72, 206, 82, 23, 90, 96, 247, 223, 177, 250, 131, 201, 115, 60, 76, 251, 209, 184, 197, 242, 122, 221, 249, 74, 62, 119, 189, 74, 191, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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