← previous blocknext block →recent activity
Analyzing
Block #90,650,789
11 transactions · 11 stateful · 2026-07-27 02:20:08 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,650,789 · 11 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
2w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa38eb2fc…1658
0x34b655…2a6f
4 touches
1 conflict
0xa38eb2fc…1659
0x34b655…2a6f
4 touches
1 conflict
0x59a61e41…ce56
0x34b655…2a6f
4 touches
1 conflict
0x9c5f6076…d3ec
0x34b655…2a6f
4 touches
1 conflict
0xf4ff6152…dac9
0x34b655…2a6f
4 touches
1 conflict
0xfb6eb5df…6c71
0x34b655…2a6f
4 touches
1 conflict
0x2547d753…e8e6
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