Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f9805ec37f2ff90ed841d06ad01fc35a43606ae1b926bdc41df386dab240c56

Tx prefix hash: 1b82f7b8ff7e8906277203d9ad36f213c2672ad5c0d0fead1c323977b6430b69
Tx public key: 8fe6bab9f837a97041f7ec9ce9366fc958c869eae6cd7d5b932e7bab464f3900
Timestamp: 1729557094 Timestamp [UCT]: 2024-10-22 00:31:34 Age [y:d:h:m:s]: 00:093:02:38:23
Block: 1136748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66540 RingCT/type: yes/0
Extra: 018fe6bab9f837a97041f7ec9ce9366fc958c869eae6cd7d5b932e7bab464f39000211000000011f0a53eb000000000000000000

1 output(s) for total of 0.607800000000 dcy

stealth address amount amount idx
00: 86d9f4e50cc12b9ef8218bb9e7e6905342e00b9e09d63a00c4229e2ba3b744a6 0.607800000000 1620111 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": 1136758, "vin": [ { "gen": { "height": 1136748 } } ], "vout": [ { "amount": 607800000, "target": { "key": "86d9f4e50cc12b9ef8218bb9e7e6905342e00b9e09d63a00c4229e2ba3b744a6" } } ], "extra": [ 1, 143, 230, 186, 185, 248, 55, 169, 112, 65, 247, 236, 156, 233, 54, 111, 201, 88, 200, 105, 234, 230, 205, 125, 91, 147, 46, 123, 171, 70, 79, 57, 0, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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