Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a75bf1cfb664e3ba11a3dfe017a5bca6f5db7b2e680b40c36d9dd3ea157a8758

Tx prefix hash: 2934dee8f3be276b6bd1a36a5080df2b77e131418bc9d3c4a8069b9ba6ea9e60
Tx public key: 382ada6acfd8ad3d970e36469b62a54a6205efa869c81874ae37da4fe5802f00
Timestamp: 1699589049 Timestamp [UCT]: 2023-11-10 04:04:09 Age [y:d:h:m:s]: 01:167:17:37:25
Block: 888347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381079 RingCT/type: yes/0
Extra: 01382ada6acfd8ad3d970e36469b62a54a6205efa869c81874ae37da4fe5802f00021100000003faf35c9c000000000000000000

1 output(s) for total of 0.699097291000 dcy

stealth address amount amount idx
00: c5f3f9402dc3639c23f6b653521f565540d1139cd0d1c9500883308630e0f315 0.699097291000 1344286 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": 888357, "vin": [ { "gen": { "height": 888347 } } ], "vout": [ { "amount": 699097291, "target": { "key": "c5f3f9402dc3639c23f6b653521f565540d1139cd0d1c9500883308630e0f315" } } ], "extra": [ 1, 56, 42, 218, 106, 207, 216, 173, 61, 151, 14, 54, 70, 155, 98, 165, 74, 98, 5, 239, 168, 105, 200, 24, 116, 174, 55, 218, 79, 229, 128, 47, 0, 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