← previous blocknext block →recent activity
Analyzing
Block #90,796,751
15 transactions · 12 stateful · 2026-07-27 14:34:26 UTC
Parallelism
67/100
Blocked
58%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,796,751 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w18w29w310w413w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8a53716…3386
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x1346ac01…31f2
0x34b655…2a6f
4 touches
1 conflict
0x5494779e…ed9b
0x34b655…2a6f
4 touches
1 conflict
0x6629b7f2…c972
0x34b655…2a6f
4 touches
1 conflict
0x79bdf655…91f2
0x34b655…2a6f
4 touches
1 conflict
0x89492cdf…3d49
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 0xa8a53716b5…2d3386
Audit this contract →
← previous block·next block →recent activity