← previous blocknext block →recent activity
Analyzing
Block #91,833,448
21 transactions · 19 stateful · 2026-07-31 05:33:03 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,833,448 · 21 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
1w02w03w04w15w16w27w28w311w112w413w518w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d299016…83f9
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x4a39a2a4…857b
0x34b655…2a6f
8 touches
6 conflicts
0xda2ee2e7…968a
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0x0d29901635…c883f9
Audit this contract →
← previous block·next block →recent activity