← previous blocknext block →recent activity
Analyzing
Block #90,839,977
15 transactions · 14 stateful · 2026-07-27 18:11:59 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,839,977 · 15 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
5w06w19w110w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa38eb2fc…1659
0x34b655…2a6f
6 touches
3 conflicts
0xe3fbd09c…9f30
0x34b655…2a6f
6 touches
3 conflicts
0xa38eb2fc…1658
0x34b655…2a6f
6 touches
3 conflicts
0x1b77e6f7…53d7
0x34b655…2a6f
4 touches
1 conflict
0x5f917ce8…a3c3
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
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 0xa38eb2fcd4…781659
Audit this contract →
← previous block·next block →recent activity