← previous blocknext block →recent activity
Analyzing
Block #91,191,863
27 transactions · 26 stateful · 2026-07-28 23:43:09 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,191,863 · 27 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
2w03w14w25w06w17w28w39w410w513w314w415w516w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb56f0740…7542
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0x48cba2…b48b
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xa24f9324…c80a
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x6ff9c682…345d
0x34b655…2a6f
6 touches
3 conflicts
0x96d8c638…762d
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
21 conflicts on slot 0xb56f0740e2…c17542
Audit this contract →
← previous block·next block →recent activity