Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e885ef96c07ddbe09be482db5268b41a57fa23cb1b37226e636d29e021b6ab49

Tx prefix hash: 84e61da30aedb3c5516944b5c0aa1a7fc11a08aed678201819af4f5e864e3b0c
Tx public key: fa0db9eb3f2c1f003c6336744ea2c7265c7cd541c21fada7cd80a6ae8802da33
Timestamp: 1703928649 Timestamp [UCT]: 2023-12-30 09:30:49 Age [y:d:h:m:s]: 01:133:23:47:19
Block: 924319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356889 RingCT/type: yes/0
Extra: 01fa0db9eb3f2c1f003c6336744ea2c7265c7cd541c21fada7cd80a6ae8802da33021100000024ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8707e8f9bee364df206ecb3b5b6d2c1bf390ddca8dc1c038f736cfa83320358 0.600000000000 1382063 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": 924329, "vin": [ { "gen": { "height": 924319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8707e8f9bee364df206ecb3b5b6d2c1bf390ddca8dc1c038f736cfa83320358" } } ], "extra": [ 1, 250, 13, 185, 235, 63, 44, 31, 0, 60, 99, 54, 116, 78, 162, 199, 38, 92, 124, 213, 65, 194, 31, 173, 167, 205, 128, 166, 174, 136, 2, 218, 51, 2, 17, 0, 0, 0, 36, 172, 50, 141, 17, 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