← previous blocknext block →recent activity
Analyzing
Block #91,100,880
24 transactions · 21 stateful · 2026-07-28 16:05:28 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,100,880 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w07w110w111w216w317w319w020w121w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a0cecef…4ed0
0x34b655…2a6f
6 touches
3 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x07d8b1e8…78c6
0x34b655…2a6f
4 touches
1 conflict
0x5bc6b706…fce6
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 0x0a0cecef55…324ed0
Audit this contract →
← previous block·next block →recent activity