← previous blocknext block →recent activity
Analyzing
Block #83,632,137
21 transactions · 19 stateful · 2026-06-25 16:00:38 UTC
Parallelism
76/100
Blocked
32%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,632,137 · 21 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
1w03w04w05w16w27w311w112w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d4b0baf…1423
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x5396d712…a139
0x34b655…2a6f
6 touches
3 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
6 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x27a129b2…2f8e
0x34b655…2a6f
4 touches
1 conflict
0x32229dd3…4dbb
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 0x1d4b0bafd5…641423
Audit this contract →
← previous block·next block →recent activity