← previous blocknext block →recent activity
Analyzing
Block #90,885,839
16 transactions · 16 stateful · 2026-07-27 22:02:44 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,885,839 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w27w38w410w111w212w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xfefce52e…6ad5
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0x731f2745…9370
0xa6afd3…d132
6 touches
3 conflicts
0x1b77e6f7…53d7
0x34b655…2a6f
6 touches
3 conflicts
0xcb578d94…6e0d
0x34b655…2a6f
6 touches
3 conflicts
0x8f203394…f2dc
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity