← previous blocknext block →recent activity
Analyzing
Block #90,819,340
14 transactions · 14 stateful · 2026-07-27 16:28:10 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,819,340 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w08w19w210w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e162301…9c1b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf0bd9219…d498
0x34b655…2a6f
4 touches
1 conflict
0x4f267385…cc89
0x34b655…2a6f
4 touches
1 conflict
0x98212952…9ba6
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4806
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 0x7e1623011b…ce9c1b
Audit this contract →
← previous block·next block →recent activity