Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 438128914be0ba42103b27073d7c3a94ca52e03e42e492e24a7be08442ea9abd

Tx prefix hash: d7670066c4f35670f0d3221efc8ba55f090894777cdfb8c9d5cee79b758473e1
Tx public key: 0c6fdd23da0a4beb25c805f12adf21bc258e7cc10a68572fb7e6ed88a49c7d46
Timestamp: 1705018662 Timestamp [UCT]: 2024-01-12 00:17:42 Age [y:d:h:m:s]: 01:027:04:12:18
Block: 933338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280508 RingCT/type: yes/0
Extra: 010c6fdd23da0a4beb25c805f12adf21bc258e7cc10a68572fb7e6ed88a49c7d460211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b0d6a4cb218bd685507bf184f51d4368a3458ad32b859b11a2976822bf6613b 0.600000000000 1391300 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": 933348, "vin": [ { "gen": { "height": 933338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b0d6a4cb218bd685507bf184f51d4368a3458ad32b859b11a2976822bf6613b" } } ], "extra": [ 1, 12, 111, 221, 35, 218, 10, 75, 235, 37, 200, 5, 241, 42, 223, 33, 188, 37, 142, 124, 193, 10, 104, 87, 47, 183, 230, 237, 136, 164, 156, 125, 70, 2, 17, 0, 0, 0, 8, 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