← previous blocknext block →recent activity
Analyzing
Block #90,856,006
8 transactions · 7 stateful · 2026-07-27 19:32:36 UTC
Parallelism
38/100
Blocked
57%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,856,006 · 8 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
1w02w14w25w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6634746e…884a
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x841e8727…0e8c
0x34b655…2a6f
4 touches
1 conflict
0xe561281f…7569
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x27754bd4…96ae
0x34b655…2a6f
4 touches
1 conflict
0xe66201d4…84f1
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 0x6634746ec3…12884a
Audit this contract →
← previous block·next block →recent activity