← previous blocknext block →recent activity
Analyzing
Block #91,019,546
14 transactions · 14 stateful · 2026-07-28 09:16:11 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,019,546 · 14 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
5w06w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85c84f98…06d7
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd99d25df…ecd8
0x34b655…2a6f
4 touches
1 conflict
0xe751731d…9aa5
0x34b655…2a6f
4 touches
1 conflict
0x0c7a4619…2b80
0x34b655…2a6f
4 touches
1 conflict
0x15eb6170…3da3
0x34b655…2a6f
4 touches
1 conflict
0x207e9f25…4724
0x34b655…2a6f
4 touches
1 conflict
0x207e9f25…4725
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
3 conflicts on slot 0x85c84f9817…2806d7
Audit this contract →
← previous block·next block →recent activity