← previous blocknext block →recent activity
Analyzing
Block #91,957,556
20 transactions · 19 stateful · 2026-07-31 15:57:27 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,957,556 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w06w17w08w19w210w011w112w215w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x248e6f5b…1db5
0x7b9256…1fb2
6 touches
3 conflicts
0x248e6f5b…1db6
0x7b9256…1fb2
6 touches
3 conflicts
0xd227c06a…48db
0x7b9256…1fb2
6 touches
3 conflicts
0xd227c06a…48dc
0x7b9256…1fb2
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
3 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity