← previous blocknext block →recent activity
Analyzing
Block #90,128,205
24 transactions · 16 stateful · 2026-07-25 06:15:17 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,128,205 · 24 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
2w03w15w17w28w113w015w016w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb2fec189…c546
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0003
0x116e7d…d8f1
4 touches
1 conflict
0xab2f6eed…254a
0x188d58…ea8e
4 touches
1 conflict
0xab2f6eed…254b
0x188d58…ea8e
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0fe1e6e0…f553
0x34b655…2a6f
4 touches
1 conflict
0x1a9064c9…c8ca
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity