← previous blocknext block →recent activity
Analyzing
Block #91,432,069
23 transactions · 23 stateful · 2026-07-29 19:53:52 UTC
Parallelism
52/100
Blocked
57%
Avg conflicts / tx
1.7
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #91,432,069 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w412w413w514w515w617w618w719w820w921w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda2ee2e7…968a
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe19cbaaf…3b90
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x966e45cf…0f25
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xfd9d2858…58c6
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
10 conflicts on slot 0xda2ee2e777…e7968a
Audit this contract →
← previous block·next block →recent activity