Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a091f2d7ddfafc0fda954893081a2f81785f133924039154f673b76d71b1e38f

Tx prefix hash: ead21dd8a62d5f52645f21b51500d420b64abd0d06034628296fc534b9ad636e
Tx public key: 5000bac5d2d725a83c39c2d0109a60f2ade8773583f3b22178e2d2c8bf800813
Timestamp: 1708262635 Timestamp [UCT]: 2024-02-18 13:23:55 Age [y:d:h:m:s]: 01:026:04:59:45
Block: 960248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279771 RingCT/type: yes/0
Extra: 015000bac5d2d725a83c39c2d0109a60f2ade8773583f3b22178e2d2c8bf8008130211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13e66bb331641dcb6ea1d79670e0e65aa72ec311434dfb8d7fd29e6b8ee6b9fa 0.600000000000 1419811 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": 960258, "vin": [ { "gen": { "height": 960248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13e66bb331641dcb6ea1d79670e0e65aa72ec311434dfb8d7fd29e6b8ee6b9fa" } } ], "extra": [ 1, 80, 0, 186, 197, 210, 215, 37, 168, 60, 57, 194, 208, 16, 154, 96, 242, 173, 232, 119, 53, 131, 243, 178, 33, 120, 226, 210, 200, 191, 128, 8, 19, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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