← previous blocknext block →recent activity
Analyzing
Block #90,881,184
5 transactions · 5 stateful · 2026-07-27 21:39:18 UTC
Parallelism
40/100
Blocked
40%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,881,184 · 5 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
0x69a45f39…39aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0ea46b1d…c9a4
0x34b655…2a6f
2 touches
0 conflicts
0x12f58c96…4ef5
0x34b655…2a6f
2 touches
0 conflicts
0x1b77e6f7…53d7
0x34b655…2a6f
2 touches
0 conflicts
0x26d65e37…ef1b
0x34b655…2a6f
2 touches
0 conflicts
0x28d022ae…69b5
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 0x69a45f39d6…c739aa
Audit this contract →
← previous block·next block →recent activity