Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caf3f2eb2d373557539d65edb42c9bce4602f871e21b78f87e20eca931f59213

Tx prefix hash: 4686f80ca4c9faf19979b1f584623139cf6eba9fc090b33c0f9d1f579653c164
Tx public key: 4aa3bd69a1b426f27a7b84a5c528ac0c88993ed3425f28e46eef6f33a6052466
Timestamp: 1694944348 Timestamp [UCT]: 2023-09-17 09:52:28 Age [y:d:h:m:s]: 01:164:09:37:51
Block: 850021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378553 RingCT/type: yes/0
Extra: 014aa3bd69a1b426f27a7b84a5c528ac0c88993ed3425f28e46eef6f33a6052466021100000003faf35c9c000000000000000000

1 output(s) for total of 0.936542786000 dcy

stealth address amount amount idx
00: 0cf59bd454c8040460a2f71090905983881913d68c489f7e6f008f4606f3448b 0.936542786000 1303715 of 0

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": 850031, "vin": [ { "gen": { "height": 850021 } } ], "vout": [ { "amount": 936542786, "target": { "key": "0cf59bd454c8040460a2f71090905983881913d68c489f7e6f008f4606f3448b" } } ], "extra": [ 1, 74, 163, 189, 105, 161, 180, 38, 242, 122, 123, 132, 165, 197, 40, 172, 12, 136, 153, 62, 211, 66, 95, 40, 228, 110, 239, 111, 51, 166, 5, 36, 102, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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