← previous blocknext block →recent activity
Analyzing
Block #90,811,486
14 transactions · 13 stateful · 2026-07-27 15:48:39 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,811,486 · 14 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
3w04w07w110w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58f0f706…46a5
0x34b655…2a6f
4 touches
1 conflict
0x6c26d635…1bbf
0x34b655…2a6f
4 touches
1 conflict
0x808cee1e…2e2f
0x34b655…2a6f
4 touches
1 conflict
0x83220a94…1bd7
0x34b655…2a6f
4 touches
1 conflict
0x833cb3bd…e138
0x34b655…2a6f
4 touches
1 conflict
0xc782a816…d172
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0cc65720…396c
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 0x58f0f7066e…1846a5
Audit this contract →
← previous block·next block →recent activity