← previous blocknext block →recent activity
Analyzing
Block #87,304,879
21 transactions · 19 stateful · 2026-07-12 16:26:01 UTC
Parallelism
76/100
Blocked
32%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,304,879 · 21 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
1w04w05w06w17w08w111w112w213w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ef0952c…762d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x225e1f26…fede
0x34b655…2a6f
4 touches
1 conflict
0x2484cc15…5afc
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x53bda555…3810
0x34b655…2a6f
4 touches
1 conflict
0x57acd0c7…48bc
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 0x3ef0952c66…03762d
Audit this contract →
← previous block·next block →recent activity