← previous blocknext block →recent activity
Analyzing
Block #83,624,162
16 transactions · 15 stateful · 2026-06-25 15:07:22 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,624,162 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w411w012w114w115w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa6f28d9…83ef
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
10 touches
10 conflicts
0x3a2ddccb…5123
0x34b655…2a6f
10 touches
10 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
10 touches
10 conflicts
0xbbec4dcb…832e
0x34b655…2a6f
10 touches
10 conflicts
0xb1c9d072…12d3
0x34b655…2a6f
8 touches
6 conflicts
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
15 conflicts on slot 0xaa6f28d94d…fa83ef
Audit this contract →
← previous block·next block →recent activity