← previous blocknext block →recent activity
Analyzing
Block #91,189,120
27 transactions · 25 stateful · 2026-07-28 23:29:21 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,189,120 · 27 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
1w02w05w19w010w111w014w116w217w319w120w423w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52b477bc…7ccf
0x34b655…2a6f
6 touches
3 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
6 touches
3 conflicts
0x966e45cf…0f25
0x34b655…2a6f
6 touches
3 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0d6d262c…958d
0x34b655…2a6f
4 touches
1 conflict
0x298155aa…b111
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 0x52b477bcb8…5d7ccf
Audit this contract →
← previous block·next block →recent activity