Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54a12937c1aac313201362ba0450b21a97edbff10a555bee006fa6944a3eef83

Tx prefix hash: 8536d03602d8e2f4bd96e109f37b4c134e29a9b04a51270c91e6bcb74f9c2f87
Tx public key: b0f26c3a34cbda943e3e2839196e129592036accf7541f89e6056772935be3af
Timestamp: 1696941433 Timestamp [UCT]: 2023-10-10 12:37:13 Age [y:d:h:m:s]: 01:159:15:07:44
Block: 866597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375117 RingCT/type: yes/0
Extra: 01b0f26c3a34cbda943e3e2839196e129592036accf7541f89e6056772935be3af0211000000014b8f5122000000000000000000

1 output(s) for total of 0.825285909000 dcy

stealth address amount amount idx
00: c9109f41dc78fb5a0cff238d558e96cc725ef6c3aecf71f99d1ae43b8c7251fd 0.825285909000 1321211 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": 866607, "vin": [ { "gen": { "height": 866597 } } ], "vout": [ { "amount": 825285909, "target": { "key": "c9109f41dc78fb5a0cff238d558e96cc725ef6c3aecf71f99d1ae43b8c7251fd" } } ], "extra": [ 1, 176, 242, 108, 58, 52, 203, 218, 148, 62, 62, 40, 57, 25, 110, 18, 149, 146, 3, 106, 204, 247, 84, 31, 137, 230, 5, 103, 114, 147, 91, 227, 175, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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