← previous blocknext block →recent activity
Analyzing
Block #90,822,181
16 transactions · 16 stateful · 2026-07-27 16:42:28 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,822,181 · 16 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
2w03w04w06w07w18w19w210w311w414w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x081b38a9…8455
0x34b655…2a6f
6 touches
3 conflicts
0x2e9d65ac…2265
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3055b4d0…81c0
0x34b655…2a6f
6 touches
3 conflicts
0x939cdd56…00c8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x9cf9008a…d826
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 0x081b38a950…da8455
Audit this contract →
← previous block·next block →recent activity