← previous blocknext block →recent activity
Analyzing
Block #83,641,113
21 transactions · 20 stateful · 2026-06-25 17:00:36 UTC
Parallelism
57/100
Blocked
50%
Avg conflicts / tx
1.1
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,641,113 · 21 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w09w110w211w312w413w514w015w117w618w719w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x049cca71…b102
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xbb3504d4…b05f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x529a94a3…ac8b
0x34b655…2a6f
4 touches
1 conflict
0x6d1160ba…890a
0x34b655…2a6f
4 touches
1 conflict
0x75291f8b…3ac0
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 0x049cca710d…16b102
Audit this contract →
← previous block·next block →recent activity