← previous blocknext block →recent activity
Analyzing
Block #91,026,612
10 transactions · 10 stateful · 2026-07-28 09:51:45 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,026,612 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e3f27ce…580c
0x34b655…2a6f
6 touches
3 conflicts
0xacca1d4f…d6df
0x34b655…2a6f
4 touches
1 conflict
0x171352be…07ab
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x2c7f2108…99fd
0x34b655…2a6f
2 touches
0 conflicts
0x41fc2b04…2805
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x3e3f27ce6e…b6580c
Audit this contract →
← previous block·next block →recent activity