Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0195e9b15d23414f8f39f7927673ca5f536d8bb68fed6e9176f9ba2a85809cf3

Tx prefix hash: 639e56ce824e9e0796c667ddeee5ee9a362d98a2c7ab65475ec666d41f1d4258
Tx public key: 9afcdd26beee1cd2bb555e0512b641724db33857fdf230d0d4f8698a6a55bd2b
Timestamp: 1728820763 Timestamp [UCT]: 2024-10-13 11:59:23 Age [y:d:h:m:s]: 00:235:01:38:48
Block: 1130688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167837 RingCT/type: yes/0
Extra: 019afcdd26beee1cd2bb555e0512b641724db33857fdf230d0d4f8698a6a55bd2b021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b54e4df95a59f8dc36dedd469ebfedd5831a1c5c25b5438a79b3bafeae7122a2 0.600000000000 1613565 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": 1130698, "vin": [ { "gen": { "height": 1130688 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b54e4df95a59f8dc36dedd469ebfedd5831a1c5c25b5438a79b3bafeae7122a2" } } ], "extra": [ 1, 154, 252, 221, 38, 190, 238, 28, 210, 187, 85, 94, 5, 18, 182, 65, 114, 77, 179, 56, 87, 253, 242, 48, 208, 212, 248, 105, 138, 106, 85, 189, 43, 2, 17, 0, 0, 0, 6, 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