← previous blocknext block →recent activity
Analyzing
Block #90,516,182
16 transactions · 14 stateful · 2026-07-26 15:03:00 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,516,182 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w09w110w112w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ec7fb56…bca1
0x34b655…2a6f
6 touches
3 conflicts
0xcbcc67c0…34de
0x34b655…2a6f
6 touches
3 conflicts
0x2aab0897…78f7
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4806
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4807
0x34b655…2a6f
4 touches
1 conflict
0x707c64bb…2fa6
0x34b655…2a6f
4 touches
1 conflict
0x8743e1ba…8331
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 0x0ec7fb56bf…a7bca1
Audit this contract →
← previous block·next block →recent activity