← previous blocknext block →recent activity
Analyzing
Block #90,976,212
20 transactions · 19 stateful · 2026-07-28 05:37:20 UTC
Parallelism
60/100
Blocked
42%
Avg conflicts / tx
1.45
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,976,212 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w07w111w212w313w414w515w616w718w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0x705ab4ae…0162
0x34b655…2a6f
12 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0x35e4d749…3a9d
0x34b655…2a6f
8 touches
6 conflicts
0xd57a704c…e488
0x34b655…2a6f
7 touches
6 conflicts
0xa57da2e8…e811
0x34b655…2a6f
5 touches
3 conflicts
0x78860c4f…cade
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity