← previous blocknext block →recent activity
Analyzing
Block #90,801,012
10 transactions · 9 stateful · 2026-07-27 14:55:53 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,801,012 · 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
2w06w17w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa110f4d8…c9eb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x1d68c976…b6e6
0x34b655…2a6f
4 touches
1 conflict
0x9ba6ae4a…90cb
0x34b655…2a6f
4 touches
1 conflict
0x073c81c5…e369
0x34b655…2a6f
2 touches
0 conflicts
0x0b62257d…8d9b
0x34b655…2a6f
2 touches
0 conflicts
0x0c233c18…37bb
0x34b655…2a6f
2 touches
0 conflicts
0x0ce18f62…c25a
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
1 conflict on slot 0xa110f4d84f…90c9eb
Audit this contract →
← previous block·next block →recent activity