← previous blocknext block →recent activity
Analyzing
Block #90,803,932
27 transactions · 21 stateful · 2026-07-27 15:10:34 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,803,932 · 27 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
2w09w010w113w114w116w218w319w423w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c27b92d…451b
0x34b655…2a6f
6 touches
3 conflicts
0xb476ee35…c627
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x28c714d9…9438
0xa6afd3…d132
4 touches
1 conflict
0x138c3780…98f4
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x37efa24e…4c72
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 0x0c27b92dc8…fc451b
Audit this contract →
← previous block·next block →recent activity