← previous blocknext block →recent activity
Analyzing
Block #90,818,674
14 transactions · 13 stateful · 2026-07-27 16:24:49 UTC
Parallelism
79/100
Blocked
15%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,818,674 · 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
5w06w07w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f1ac759…b8fb
0x34b655…2a6f
6 touches
3 conflicts
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xb54c8ced…5b8c
0x34b655…2a6f
4 touches
1 conflict
0xc6000ba5…8d65
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcbe9b09a…4988
0x080ec9…fe74
2 touches
0 conflicts
0xe8adf936…34b0
0x188d58…ea8e
2 touches
0 conflicts
0xe8adf936…34b1
0x188d58…ea8e
2 touches
0 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
3 conflicts on slot 0x1f1ac759f8…11b8fb
Audit this contract →
← previous block·next block →recent activity