← previous blocknext block →recent activity
Analyzing
Block #90,042,732
10 transactions · 10 stateful · 2026-07-24 23:01:33 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,042,732 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08024b2c…d265
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0db691ab…3ee3
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
2 touches
0 conflicts
0x1b25f260…c42a
0x34b655…2a6f
2 touches
0 conflicts
0x2e9d65ac…2265
0x34b655…2a6f
2 touches
0 conflicts
0x2e9d65ac…2266
0x34b655…2a6f
2 touches
0 conflicts
0x6286099d…2152
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x08024b2c16…37d265
Audit this contract →
← previous block·next block →recent activity