← previous blocknext block →recent activity
Analyzing
Block #91,103,408
21 transactions · 20 stateful · 2026-07-28 16:18:11 UTC
Parallelism
81/100
Blocked
20%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,103,408 · 21 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
2w03w14w25w315w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7be3246e…f89f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x383e75cc…b79f
0x34b655…2a6f
6 touches
3 conflicts
0xde284bf5…ab21
0x34b655…2a6f
6 touches
3 conflicts
0x388b63a9…5008
0x34b655…2a6f
4 touches
1 conflict
0xe1b6b3c8…6676
0x34b655…2a6f
4 touches
1 conflict
0x709c2293…6c55
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity