Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0746a9c035cf5be55bc295b0a80a691948e691d465fcac0d7f9b3dd455f30f2a

Tx prefix hash: d65952b27aea59def87856a2f324b72849b468f4d3db851da2705ec5ce75d80d
Tx public key: ddd9578e17d0f69ed696e887036855353d089a4d67cd2694704675f80a52817c
Timestamp: 1724669385 Timestamp [UCT]: 2024-08-26 10:49:45 Age [y:d:h:m:s]: 01:065:18:30:43
Block: 1096256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305464 RingCT/type: yes/0
Extra: 01ddd9578e17d0f69ed696e887036855353d089a4d67cd2694704675f80a52817c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5eeb312aa299fae5a4b24a2e47d54a429dbedbb9b248b32ab5a6d93b17a4bb5 0.600000000000 1571443 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": 1096266, "vin": [ { "gen": { "height": 1096256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5eeb312aa299fae5a4b24a2e47d54a429dbedbb9b248b32ab5a6d93b17a4bb5" } } ], "extra": [ 1, 221, 217, 87, 142, 23, 208, 246, 158, 214, 150, 232, 135, 3, 104, 85, 53, 61, 8, 154, 77, 103, 205, 38, 148, 112, 70, 117, 248, 10, 82, 129, 124, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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