← previous blocknext block →recent activity
Analyzing
Block #90,890,377
9 transactions · 8 stateful · 2026-07-27 22:25:33 UTC
Parallelism
44/100
Blocked
63%
Avg conflicts / tx
1.22
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,890,377 · 9 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
1w02w14w25w36w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5655f5c3…6b75
0x34b655…2a6f
8 touches
6 conflicts
0xabd0bcfc…64e2
0x34b655…2a6f
6 touches
3 conflicts
0x9ba6ae4a…90cb
0x34b655…2a6f
6 touches
3 conflicts
0xf6818217…345a
0x34b655…2a6f
6 touches
3 conflicts
0x82e925dc…9938
0x34b655…2a6f
4 touches
1 conflict
0x424d48b2…e6ae
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
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
6 conflicts on slot 0x5655f5c3b4…dd6b75
Audit this contract →
← previous block·next block →recent activity