← previous blocknext block →recent activity
Analyzing
Block #91,136,761
13 transactions · 11 stateful · 2026-07-28 19:05:57 UTC
Parallelism
54/100
Blocked
64%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,136,761 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w48w49w512w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4e0a934…5fc7
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x3b9bb58c…e73a
0x34b655…2a6f
6 touches
3 conflicts
0x60a899fe…e7a2
0x34b655…2a6f
6 touches
3 conflicts
0x7150753f…7e32
0x34b655…2a6f
6 touches
3 conflicts
0xe1bde870…d9ac
0x34b655…2a6f
6 touches
3 conflicts
0x5babb0df…9cf9
0x34b655…2a6f
6 touches
3 conflicts
0xf346808d…6ad4
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
6 conflicts on slot 0xb4e0a934b9…435fc7
Audit this contract →
← previous block·next block →recent activity