← previous blocknext block →recent activity
Analyzing
Block #91,971,617
15 transactions · 15 stateful · 2026-07-31 17:08:10 UTC
Parallelism
47/100
Blocked
53%
Avg conflicts / tx
1.73
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,971,617 · 15 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w19w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02991b41…19e6
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc3760fc6…b07c
0x34b655…2a6f
6 touches
3 conflicts
0x69a64a5c…0000
0x34b655…2a6f
6 touches
3 conflicts
0x170e4e4c…2b90
0x34b655…2a6f
6 touches
3 conflicts
0xe487099a…0f14
0x34b655…2a6f
6 touches
3 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 0x02991b41c5…1a19e6
Audit this contract →
← previous block·next block →recent activity