← previous blocknext block →recent activity
Analyzing
Block #90,880,105
11 transactions · 10 stateful · 2026-07-27 21:33:53 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,880,105 · 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
1w02w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x739a54da…8647
0x34b655…2a6f
6 touches
3 conflicts
0x99c5409a…25b7
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00f6a8a7…0e6e
0x34b655…2a6f
4 touches
1 conflict
0x923c57f1…7810
0x34b655…2a6f
2 touches
0 conflicts
0xa243ce39…3ff4
0x34b655…2a6f
2 touches
0 conflicts
0xa9660e2b…64df
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 0x739a54daae…c08647
Audit this contract →
← previous block·next block →recent activity