← previous blocknext block →recent activity
Analyzing
Block #91,103,706
15 transactions · 15 stateful · 2026-07-28 16:19:41 UTC
Parallelism
73/100
Blocked
47%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,103,706 · 15 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
1w03w04w15w28w19w211w213w114w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb4f8cd9…d014
0x34b655…2a6f
6 touches
3 conflicts
0x1a7adb59…a2c8
0x34b655…2a6f
4 touches
1 conflict
0x28ceceef…ecc2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5060cdde…445d
0x34b655…2a6f
4 touches
1 conflict
0x5502e1cc…3910
0x34b655…2a6f
4 touches
1 conflict
0x659e6618…dfa7
0x34b655…2a6f
4 touches
1 conflict
0x65f90aa4…c97f
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 0xfb4f8cd98d…bcd014
Audit this contract →
← previous block·next block →recent activity