← previous blocknext block →recent activity
Analyzing
Block #89,858,925
20 transactions · 15 stateful · 2026-07-24 07:36:15 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,858,925 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w016w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0bcbbcad…fc9c
0x34b655…2a6f
6 touches
3 conflicts
0xed16d4ce…a66e
0x34b655…2a6f
6 touches
3 conflicts
0xd5a69b22…63e3
0xd32edf…ff58
5 touches
3 conflicts
0x54836d65…80ab
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x34a2c248…f7ed
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity