← previous blocknext block →recent activity
Analyzing
Block #87,594,699
45 transactions · 32 stateful · 2026-07-14 00:45:02 UTC
Parallelism
69/100
Blocked
69%
Avg conflicts / tx
2.27
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,594,699 · 45 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w17w28w09w110w211w019w120w221w322w423w524w625w726w827w928w1029w1130w1231w1333w336w137w1344w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
26 touches
78 conflicts
0x077d58c3…8ed7
0x34b655…2a6f
8 touches
6 conflicts
0x0bce8fb9…edb6
0x34b655…2a6f
8 touches
6 conflicts
0x17f2c132…ca5f
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x26050074…6967
0x34b655…2a6f
8 touches
6 conflicts
0x2dfde2ed…8801
0x34b655…2a6f
8 touches
6 conflicts
0x42341814…60f1
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
78 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity