← previous blocknext block →recent activity
Analyzing
Block #90,611,289
6 transactions · 5 stateful · 2026-07-26 23:01:25 UTC
Parallelism
50/100
Blocked
40%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,611,289 · 6 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x93b6fab0…09d6
0x34b655…2a6f
4 touches
1 conflict
0x0b7ff287…d1ba
0x34b655…2a6f
2 touches
0 conflicts
0x0bcbbcad…fc9c
0x34b655…2a6f
2 touches
0 conflicts
0x0c53719e…0366
0x34b655…2a6f
2 touches
0 conflicts
0x0dd3bdfb…7537
0x34b655…2a6f
2 touches
0 conflicts
0x0dd3bdfb…7538
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 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity