← previous blocknext block →recent activity
Analyzing
Block #91,968,127
24 transactions · 21 stateful · 2026-07-31 16:50:37 UTC
Parallelism
67/100
Blocked
62%
Avg conflicts / tx
1.83
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,968,127 · 24 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
1w02w13w24w05w16w27w38w49w510w615w717w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87be5077…5a5b
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x27034002…2f27
0x34b655…2a6f
8 touches
6 conflicts
0xf9874e36…beed
0x34b655…2a6f
6 touches
3 conflicts
0x2a34bb88…04d5
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
21 conflicts on slot 0x87be507714…415a5b
Audit this contract →
← previous block·next block →recent activity