← previous blocknext block →recent activity
Analyzing
Block #91,100,687
14 transactions · 14 stateful · 2026-07-28 16:04:30 UTC
Parallelism
43/100
Blocked
64%
Avg conflicts / tx
2.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,100,687 · 14 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
1w02w13w25w36w27w38w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0x737acb78…fce8
0x34b655…2a6f
16 touches
28 conflicts
0xce06a0f7…efef
0x34b655…2a6f
12 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
6 touches
3 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
6 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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity