Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad13ed229994620a62a9283cfd337c950a6b483d972df3325f4783d36d6b950f

Tx prefix hash: b549975c9e7b5d04f68258ec157f944630e763e839ef49f591497fb79768f355
Tx public key: c602913bc424b8d5d70a1367471b792e0bfa451d11b7c93da26f013533c9d1eb
Timestamp: 1695471737 Timestamp [UCT]: 2023-09-23 12:22:17 Age [y:d:h:m:s]: 01:121:18:20:58
Block: 854400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348278 RingCT/type: yes/0
Extra: 01c602913bc424b8d5d70a1367471b792e0bfa451d11b7c93da26f013533c9d1eb02110000000233af99f4000000000000000000

1 output(s) for total of 0.905770500000 dcy

stealth address amount amount idx
00: 36c8bdbe06a30833cce0cbc74dd5a71a7e95dbd04b603b3562a44fedeb91bd5e 0.905770500000 1308372 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": 854410, "vin": [ { "gen": { "height": 854400 } } ], "vout": [ { "amount": 905770500, "target": { "key": "36c8bdbe06a30833cce0cbc74dd5a71a7e95dbd04b603b3562a44fedeb91bd5e" } } ], "extra": [ 1, 198, 2, 145, 59, 196, 36, 184, 213, 215, 10, 19, 103, 71, 27, 121, 46, 11, 250, 69, 29, 17, 183, 201, 61, 162, 111, 1, 53, 51, 201, 209, 235, 2, 17, 0, 0, 0, 2, 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