← previous blocknext block →recent activity
Analyzing
Block #91,158,812
10 transactions · 9 stateful · 2026-07-28 20:56:53 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,158,812 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53a7111b…8897
0x34b655…2a6f
4 touches
1 conflict
0x421099c9…8896
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7182a94f…dc78
0x34b655…2a6f
4 touches
1 conflict
0x3ed4afeb…e199
0x34b655…2a6f
2 touches
0 conflicts
0x4b3971e6…93ec
0x34b655…2a6f
2 touches
0 conflicts
0x4ca81ae8…01d4
0x34b655…2a6f
2 touches
0 conflicts
0x55cf4758…265c
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x53a7111b60…218897
Audit this contract →
← previous block·next block →recent activity