← previous blocknext block →recent activity
Analyzing
Block #90,386,159
13 transactions · 12 stateful · 2026-07-26 04:02:41 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,386,159 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x496ff651…1310
0x34b655…2a6f
4 touches
1 conflict
0xa7d3e24a…0eb8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x18d2360f…3ee4
0x34b655…2a6f
2 touches
0 conflicts
0x2fd48b4a…4d5a
0x34b655…2a6f
2 touches
0 conflicts
0x30e3f228…0d43
0x34b655…2a6f
2 touches
0 conflicts
0x344bc09a…942f
0x34b655…2a6f
2 touches
0 conflicts
0x403a9b02…bdac
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
1 conflict on slot 0x496ff65132…401310
Audit this contract →
← previous block·next block →recent activity