Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 433e8d827a4fefd613f2f9f5a6ef6194411c17a350db97dc01dc23b6e9fbb6e0

Tx prefix hash: 8e13a6a8d2abd960c9f59b3399ab528d8de46e1befd450ee1a1bfebee8527a6f
Tx public key: bc757f8cd2a35e475555fa16b53aff99d22730e96cae4850a34f13d49bd267af
Timestamp: 1713957324 Timestamp [UCT]: 2024-04-24 11:15:24 Age [y:d:h:m:s]: 00:150:02:55:09
Block: 1007462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107530 RingCT/type: yes/0
Extra: 01bc757f8cd2a35e475555fa16b53aff99d22730e96cae4850a34f13d49bd267af0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a92eaf8e84f242792dfc83c6aa9f231415e5f3fde06fba3b23efbe54359c8c5 0.600000000000 1468810 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": 1007472, "vin": [ { "gen": { "height": 1007462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a92eaf8e84f242792dfc83c6aa9f231415e5f3fde06fba3b23efbe54359c8c5" } } ], "extra": [ 1, 188, 117, 127, 140, 210, 163, 94, 71, 85, 85, 250, 22, 181, 58, 255, 153, 210, 39, 48, 233, 108, 174, 72, 80, 163, 79, 19, 212, 155, 210, 103, 175, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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