← previous blocknext block →recent activity
Analyzing
Block #91,001,762
10 transactions · 9 stateful · 2026-07-28 07:46:23 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,001,762 · 10 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
1w03w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc85f42b6…6f23
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4c619b7d…f4fa
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0ea00063…777f
0x34b655…2a6f
2 touches
0 conflicts
0x127a4390…8e60
0x34b655…2a6f
2 touches
0 conflicts
0x1c8753e8…d214
0x34b655…2a6f
2 touches
0 conflicts
0x442e26a3…e968
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 0xc85f42b605…b36f23
Audit this contract →
← previous block·next block →recent activity