← previous blocknext block →recent activity
Analyzing
Block #90,523,830
24 transactions · 19 stateful · 2026-07-26 15:41:28 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,523,830 · 24 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
2w04w05w16w07w18w29w310w415w116w217w318w022w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
6 touches
3 conflicts
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0xd708bac6…2e5d
0x34b655…2a6f
6 touches
3 conflicts
0xe6df4062…2966
0x34b655…2a6f
6 touches
3 conflicts
0x439cfb2c…7b9e
0xa6afd3…d132
6 touches
3 conflicts
0x89678d1b…463e
0xa6afd3…d132
6 touches
3 conflicts
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity