← previous blocknext block →recent activity
Analyzing
Block #91,106,604
11 transactions · 11 stateful · 2026-07-28 16:34:16 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,106,604 · 11 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
1w02w03w14w25w38w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x4f89e431…499f
0x34b655…2a6f
4 touches
1 conflict
0xb6aedce9…a483
0x34b655…2a6f
4 touches
1 conflict
0xf4f9cac7…fd98
0x34b655…2a6f
4 touches
1 conflict
0x7150753f…7e32
0x34b655…2a6f
4 touches
1 conflict
0x7dbdf8e0…22b4
0x34b655…2a6f
4 touches
1 conflict
0xb6b61477…ed3e
0x34b655…2a6f
2 touches
0 conflicts
0xc56d6548…50a4
0x34b655…2a6f
2 touches
0 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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity