← previous blocknext block →recent activity
Analyzing
Block #90,328,644
11 transactions · 10 stateful · 2026-07-25 23:07:53 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,328,644 · 11 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
2w03w15w26w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5af098c7…4806
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4807
0x34b655…2a6f
4 touches
1 conflict
0x651d4cdd…66a6
0x34b655…2a6f
4 touches
1 conflict
0x651d4cdd…66a7
0x34b655…2a6f
4 touches
1 conflict
0x7177cd57…21ad
0x34b655…2a6f
4 touches
1 conflict
0x81238469…de5d
0x34b655…2a6f
4 touches
1 conflict
0xa5811d93…8c73
0x34b655…2a6f
4 touches
1 conflict
0xabdd2a0a…1eef
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
1 conflict on slot 0x5af098c77e…e94806
Audit this contract →
← previous block·next block →recent activity