← previous blocknext block →recent activity
Analyzing
Block #90,957,910
14 transactions · 13 stateful · 2026-07-28 04:05:16 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,957,910 · 14 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
2w03w14w27w38w49w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c22eb60…d3e2
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc60a1f10…d727
0x34b655…2a6f
6 touches
3 conflicts
0x9a73834c…0f51
0x34b655…2a6f
6 touches
3 conflicts
0x9a73834c…0f52
0x34b655…2a6f
6 touches
3 conflicts
0xb2fa1675…4e07
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
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 0x1c22eb60d7…bdd3e2
Audit this contract →
← previous block·next block →recent activity