← previous blocknext block →recent activity
Analyzing
Block #90,917,733
18 transactions · 14 stateful · 2026-07-28 00:43:11 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,917,733 · 18 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
1w06w07w18w29w010w111w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x0d2de0f6…e6c6
0x34b655…2a6f
4 touches
1 conflict
0x167de262…f61f
0x34b655…2a6f
4 touches
1 conflict
0x21c9fd73…dae4
0x34b655…2a6f
4 touches
1 conflict
0x259529eb…1015
0x34b655…2a6f
4 touches
1 conflict
0x2fade833…5de4
0x34b655…2a6f
4 touches
1 conflict
0x3c0c2f32…c3df
0x34b655…2a6f
4 touches
1 conflict
0x3faf06e8…bbe7
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity