← previous blocknext block →recent activity
Analyzing
Block #90,866,789
11 transactions · 11 stateful · 2026-07-27 20:26:55 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,866,789 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w27w38w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb15c58ec…bd83
0x34b655…2a6f
8 touches
6 conflicts
0x41c66186…229a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x2bad40ae…0522
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x65487580…b5eb
0x34b655…2a6f
6 touches
3 conflicts
0x3cf268ef…7915
0x34b655…2a6f
5 touches
3 conflicts
0xc824469a…641d
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 0xb15c58ec9b…35bd83
Audit this contract →
← previous block·next block →recent activity