← previous blocknext block →recent activity
Analyzing
Block #91,063,322
8 transactions · 7 stateful · 2026-07-28 12:56:26 UTC
Parallelism
50/100
Blocked
43%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,063,322 · 8 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4efae872…6aa8
0x34b655…2a6f
6 touches
3 conflicts
0xacd1b162…bee6
0x34b655…2a6f
6 touches
3 conflicts
0xf4ba8a46…df01
0x34b655…2a6f
4 touches
1 conflict
0x296b498d…22e2
0x34b655…2a6f
4 touches
1 conflict
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
0x41469894…5990
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa6b48d6e…0705
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
3 conflicts on slot 0x4efae87285…886aa8
Audit this contract →
← previous block·next block →recent activity