← previous blocknext block →recent activity
Analyzing
Block #90,237,284
16 transactions · 16 stateful · 2026-07-25 15:25:06 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,237,284 · 16 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
1w02w13w26w07w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xa8a53716…3386
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x2f702750…347d
0x34b655…2a6f
4 touches
1 conflict
0x487aa334…7ef2
0x34b655…2a6f
4 touches
1 conflict
0x4ca81ae8…01d4
0x34b655…2a6f
4 touches
1 conflict
0x6ae60600…5bc4
0x34b655…2a6f
4 touches
1 conflict
0x6b0d2ce5…ff19
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity