← previous blocknext block →recent activity
Analyzing
Block #87,753,943
42 transactions · 35 stateful · 2026-07-14 18:30:09 UTC
Parallelism
62/100
Blocked
57%
Avg conflicts / tx
2.17
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,753,943 · 42 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w17w015w116w218w319w420w521w622w723w824w925w1033w534w237w1138w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
10 touches
10 conflicts
0x648bb928…97f2
0x34b655…2a6f
8 touches
6 conflicts
0x6ca32a09…4e48
0x34b655…2a6f
8 touches
6 conflicts
0x2f461725…5ab2
0x34b655…2a6f
8 touches
6 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
8 touches
6 conflicts
0xa92c8763…6d7f
0x34b655…2a6f
8 touches
6 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
45 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity