← previous blocknext block →recent activity
Analyzing
Block #83,635,972
22 transactions · 22 stateful · 2026-06-25 16:26:16 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,635,972 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w07w19w010w111w212w313w415w216w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x670c5ce1…ec90
0x34b655…2a6f
6 touches
3 conflicts
0xec85756f…0ba2
0x34b655…2a6f
6 touches
3 conflicts
0x3f4dc602…5a18
0x34b655…2a6f
6 touches
3 conflicts
0xab36e9c0…ab66
0x34b655…2a6f
4 touches
1 conflict
0xb2269b61…6820
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcffc17bc…3544
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity