Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e9bcc204bb413bf939ed42426ccaed73d4e5d8f3bdcbed4b433f176724744e2

Tx prefix hash: 0c91fae990a871f72e4965fc03a79c6c682dd620e81d5ead598f775531f560b1
Tx public key: 99ae26333f7a23a53345b53b4a3aeaf9c34cabd6be376251b1c786f3b52ee871
Timestamp: 1735813525 Timestamp [UCT]: 2025-01-02 10:25:25 Age [y:d:h:m:s]: 00:166:15:50:52
Block: 1188528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118827 RingCT/type: yes/0
Extra: 0199ae26333f7a23a53345b53b4a3aeaf9c34cabd6be376251b1c786f3b52ee87102110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d8134fbb82b8e8d30fdb6ae2edb86847d7d6f75a7d15d7343e3df634d722fa1 0.600000000000 1675029 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": 1188538, "vin": [ { "gen": { "height": 1188528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d8134fbb82b8e8d30fdb6ae2edb86847d7d6f75a7d15d7343e3df634d722fa1" } } ], "extra": [ 1, 153, 174, 38, 51, 63, 122, 35, 165, 51, 69, 181, 59, 74, 58, 234, 249, 195, 76, 171, 214, 190, 55, 98, 81, 177, 199, 134, 243, 181, 46, 232, 113, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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