← previous blocknext block →recent activity
Analyzing
Block #91,295,939
13 transactions · 12 stateful · 2026-07-29 08:27:35 UTC
Parallelism
54/100
Blocked
50%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,295,939 · 13 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
1w03w15w26w37w49w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d158563…8713
0x34b655…2a6f
8 touches
6 conflicts
0x84068614…8971
0x34b655…2a6f
8 touches
6 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xadc92aaf…3077
0x34b655…2a6f
4 touches
1 conflict
0xba9f9225…2ead
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 0x3d1585630c…178713
Audit this contract →
← previous block·next block →recent activity