← previous blocknext block →recent activity
Analyzing
Block #91,405,492
11 transactions · 10 stateful · 2026-07-29 17:39:00 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,405,492 · 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
7w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d7f309d…5145
0x34b655…2a6f
8 touches
6 conflicts
0xea16a720…209b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xebc8c0af…c329
0x34b655…2a6f
6 touches
3 conflicts
0x17528ba5…099d
0x34b655…2a6f
6 touches
3 conflicts
0xb25fa8e2…c9ef
0x34b655…2a6f
6 touches
3 conflicts
0xbba9dcbb…e4c9
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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 0x5d7f309de2…775145
Audit this contract →
← previous block·next block →recent activity