← previous blocknext block →recent activity
Analyzing
Block #90,387,353
10 transactions · 9 stateful · 2026-07-26 04:08:49 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,387,353 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf51ec09c…b4a9
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x283a662b…c457
0x34b655…2a6f
6 touches
3 conflicts
0xac8a5059…fd42
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa279b18d…63bc
0x34b655…2a6f
4 touches
1 conflict
0x991e2e20…94a6
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 0xf51ec09cc1…a1b4a9
Audit this contract →
← previous block·next block →recent activity