← previous blocknext block →recent activity
Analyzing
Block #90,960,911
11 transactions · 11 stateful · 2026-07-28 04:20:21 UTC
Parallelism
82/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,960,911 · 11 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
1w02w13w16w07w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0474128…ef4e
0x7b9256…1fb2
4 touches
1 conflict
0xdbadf6b0…43b2
0x33176b…e078
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x68bec689…fccd
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x97d93dbb…6b40
0x34b655…2a6f
4 touches
1 conflict
0xddbe18ed…2158
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: 0x7b9256fd…e21fb2
1 conflict on slot 0xe04741283e…e1ef4e
Audit this contract →
← previous block·next block →recent activity