Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b67fee4d1557c0206df05c75737b8e1b7293adcc0ed5ea15b592bc769b22cd74

Tx prefix hash: ac5260262fdd072e82f8e0508448f7ce20d8edb1d3d9bba7483f459a765fe144
Tx public key: f9fa4a95f4d4e55761e467aa5178278019d809d4216faf701f6dd19d52a61eb2
Timestamp: 1706878730 Timestamp [UCT]: 2024-02-02 12:58:50 Age [y:d:h:m:s]: 01:061:05:44:08
Block: 948764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304823 RingCT/type: yes/0
Extra: 01f9fa4a95f4d4e55761e467aa5178278019d809d4216faf701f6dd19d52a61eb202110000000f52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bba41c699c3fd70f89eafd7a0c3aaca5a4686b819169202c00903d281ab3c503 0.600000000000 1407242 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": 948774, "vin": [ { "gen": { "height": 948764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bba41c699c3fd70f89eafd7a0c3aaca5a4686b819169202c00903d281ab3c503" } } ], "extra": [ 1, 249, 250, 74, 149, 244, 212, 229, 87, 97, 228, 103, 170, 81, 120, 39, 128, 25, 216, 9, 212, 33, 111, 175, 112, 31, 109, 209, 157, 82, 166, 30, 178, 2, 17, 0, 0, 0, 15, 82, 212, 126, 148, 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