← previous blocknext block →recent activity
Analyzing
Block #90,237,320
18 transactions · 17 stateful · 2026-07-25 15:25:16 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,237,320 · 18 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
2w04w15w06w19w211w314w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ead5a0b…3978
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x04e17b28…d9ef
0x34b655…2a6f
4 touches
1 conflict
0x04e17b28…d9f0
0x34b655…2a6f
4 touches
1 conflict
0x08b68583…01a1
0x34b655…2a6f
4 touches
1 conflict
0x1cad6e62…80bb
0x34b655…2a6f
4 touches
1 conflict
0x1d082421…ff2d
0x34b655…2a6f
4 touches
1 conflict
0x4f267385…cc89
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 0x2ead5a0bbd…003978
Audit this contract →
← previous block·next block →recent activity