← previous blocknext block →recent activity
Analyzing
Block #90,854,730
11 transactions · 9 stateful · 2026-07-27 19:26:11 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,854,730 · 11 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
3w05w16w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xa28e4ddb…10e5
0x34b655…2a6f
4 touches
1 conflict
0xd58e5c6b…7188
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x11a90f82…8bb6
0x34b655…2a6f
4 touches
1 conflict
0x2089dcc1…8f89
0x34b655…2a6f
2 touches
0 conflicts
0x33fa9eab…4b3d
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity