← previous blocknext block →recent activity
Analyzing
Block #91,104,792
20 transactions · 17 stateful · 2026-07-28 16:25:08 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,104,792 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w212w313w415w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0x16ca898b…f2b0
0x34b655…2a6f
8 touches
6 conflicts
0x705ab4ae…0162
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x7d1a4e77…57d9
0x34b655…2a6f
8 touches
6 conflicts
0xc861af66…5cdc
0x34b655…2a6f
6 touches
3 conflicts
0x5b3e008a…4aa9
0x34b655…2a6f
5 touches
3 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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity