← previous blocknext block →recent activity
Analyzing
Block #90,820,744
28 transactions · 23 stateful · 2026-07-27 16:35:14 UTC
Parallelism
86/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,820,744 · 28 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
1w02w13w06w07w113w014w115w218w320w122w225w026w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x449d101e…ea3f
0xa6afd3…d132
6 touches
3 conflicts
0xbd2025f0…1afd
0x34b655…2a6f
6 touches
3 conflicts
0x2130a548…c1de
0x34b655…2a6f
6 touches
3 conflicts
0x8218911e…3bed
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity