← previous blocknext block →recent activity
Analyzing
Block #90,821,403
24 transactions · 19 stateful · 2026-07-27 16:38:33 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,821,403 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w07w110w011w112w118w219w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3e0065ad…e39b
0x34b655…2a6f
8 touches
6 conflicts
0x38628dc5…cdc4
0x34b655…2a6f
6 touches
3 conflicts
0x0d4b170b…8f0e
0x34b655…2a6f
6 touches
3 conflicts
0x0d488000…3831
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x449d101e…ea3f
0xa6afd3…d132
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity