← previous blocknext block →recent activity
Analyzing
Block #90,240,962
24 transactions · 20 stateful · 2026-07-25 15:43:39 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.75
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,240,962 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w210w011w118w320w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x96dd83e6…a507
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x48050070…28ec
0x34b655…2a6f
4 touches
1 conflict
0x487aa334…7ef2
0x34b655…2a6f
4 touches
1 conflict
0x493b2422…4a08
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x6fb92ed4…7205
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity