← previous blocknext block →recent activity
Analyzing
Block #91,249,455
16 transactions · 15 stateful · 2026-07-29 04:32:55 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,249,455 · 16 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
1w02w03w14w25w26w37w48w512w013w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x259ed0cc…bef9
0x34b655…2a6f
4 touches
1 conflict
0x259ed0cc…befa
0x34b655…2a6f
4 touches
1 conflict
0x49237e5b…0909
0x34b655…2a6f
4 touches
1 conflict
0x539ac47f…eb6f
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity