← previous blocknext block →recent activity
Analyzing
Block #90,052,939
13 transactions · 11 stateful · 2026-07-24 23:52:55 UTC
Parallelism
54/100
Blocked
55%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,052,939 · 13 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
2w04w15w29w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d488000…3831
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb54facbb…1914
0x34b655…2a6f
6 touches
3 conflicts
0x55955f0b…6085
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x9fd372a1…a959
0x34b655…2a6f
6 touches
3 conflicts
0x05c3bda4…de90
0x34b655…2a6f
6 touches
3 conflicts
0x9fd37234…2731
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
6 conflicts on slot 0x0d488000e2…143831
Audit this contract →
← previous block·next block →recent activity