← previous blocknext block →recent activity
Analyzing
Block #83,400,983
16 transactions · 15 stateful · 2026-06-24 14:17:50 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,400,983 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w313w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xef3a4217…dec8
0x34b655…2a6f
6 touches
3 conflicts
0x2004b5f1…ff98
0x34b655…2a6f
6 touches
3 conflicts
0x89a8c952…58b9
0x34b655…2a6f
6 touches
3 conflicts
0x9b5a901d…3228
0xd32edf…ff58
5 touches
3 conflicts
0x2bbc0cfb…c2c1
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0f093d31…f626
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity