← previous blocknext block →recent activity
Analyzing
Block #90,234,083
11 transactions · 11 stateful · 2026-07-25 15:08:58 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,234,083 · 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
3w04w16w27w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf28d07b9…4fb2
0x34b655…2a6f
4 touches
1 conflict
0x8d37e1d9…f1f7
0x34b655…2a6f
4 touches
1 conflict
0xa4981351…e407
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe0c7c055…8db3
0x34b655…2a6f
4 touches
1 conflict
0xe0e2ffb5…9e33
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x1b244003…c9cf
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
1 conflict on slot 0xf28d07b905…5f4fb2
Audit this contract →
← previous block·next block →recent activity