← previous blocknext block →recent activity
Analyzing
Block #91,096,335
18 transactions · 18 stateful · 2026-07-28 15:42:36 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,096,335 · 18 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
4w05w16w210w211w012w113w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0xce06a0f7…efef
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49fd8382…0a3b
0x34b655…2a6f
6 touches
3 conflicts
0xf0349af4…33a6
0x34b655…2a6f
4 touches
1 conflict
0x28ceceef…ecc2
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
15 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity