← previous blocknext block →recent activity
Analyzing
Block #91,424,262
24 transactions · 21 stateful · 2026-07-29 19:13:51 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,424,262 · 24 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
1w02w13w210w012w013w014w116w220w021w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefcdf197…96a2
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe81f8eb4…e4d1
0x34b655…2a6f
6 touches
3 conflicts
0x7aa02e1c…9abb
0xd32edf…ff58
5 touches
3 conflicts
0x7e06d07b…36af
0x34b655…2a6f
4 touches
1 conflict
0x7e06d07b…36b0
0x34b655…2a6f
4 touches
1 conflict
0x8172efe5…911c
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
3 conflicts on slot 0xefcdf19725…1096a2
Audit this contract →
← previous block·next block →recent activity