← previous blocknext block →recent activity
Analyzing
Block #90,822,226
20 transactions · 19 stateful · 2026-07-27 16:42:41 UTC
Parallelism
75/100
Blocked
26%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,822,226 · 20 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
2w04w05w16w28w39w412w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e0065ad…e39b
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x107b89e4…470d
0x34b655…2a6f
4 touches
1 conflict
0x1aa62c36…420a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x25408cc8…cde7
0x34b655…2a6f
4 touches
1 conflict
0x30871fa4…1eba
0x34b655…2a6f
4 touches
1 conflict
0x3732c6c9…ded6
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 0x3e0065ad02…f8e39b
Audit this contract →
← previous block·next block →recent activity