← previous blocknext block →recent activity
Analyzing
Block #90,801,489
10 transactions · 8 stateful · 2026-07-27 14:58:17 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,801,489 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x428b6e5b…8909
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x6676e87f…b88f
0x2a68ba…90c5
2 touches
0 conflicts
0xdaf4f143…58d4
0x2a68ba…90c5
2 touches
0 conflicts
0x145572fe…b729
0x34b655…2a6f
2 touches
0 conflicts
0x369883e3…a449
0x34b655…2a6f
2 touches
0 conflicts
0x3eede796…d745
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 0x428b6e5b99…c18909
Audit this contract →
← previous block·next block →recent activity