Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9cae625373c7ed132bf4dc6fe7de1ceb9d5e02d4a0ee2e4148d18031d536012

Tx prefix hash: 9e389e106db9061b14c84ebbc889f99e875670fc230e624985301f0677c64ff7
Tx public key: 0c2b7a2e5f1c3073030e36f6215c2595bb5bf28577f049219d243a71a2fe3f43
Timestamp: 1713983010 Timestamp [UCT]: 2024-04-24 18:23:30 Age [y:d:h:m:s]: 00:347:16:12:54
Block: 1007668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248539 RingCT/type: yes/0
Extra: 010c2b7a2e5f1c3073030e36f6215c2595bb5bf28577f049219d243a71a2fe3f430211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02599519f4e11034b31a78549ab1b58988a5ae8edfa026928c612bf011a9368b 0.600000000000 1469082 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": 1007678, "vin": [ { "gen": { "height": 1007668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02599519f4e11034b31a78549ab1b58988a5ae8edfa026928c612bf011a9368b" } } ], "extra": [ 1, 12, 43, 122, 46, 95, 28, 48, 115, 3, 14, 54, 246, 33, 92, 37, 149, 187, 91, 242, 133, 119, 240, 73, 33, 157, 36, 58, 113, 162, 254, 63, 67, 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