← previous blocknext block →recent activity
Analyzing
Block #87,703,694
30 transactions · 30 stateful · 2026-07-14 12:53:48 UTC
Parallelism
73/100
Blocked
50%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,703,694 · 30 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
4w06w17w28w39w410w511w113w627w628w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfc21d7c…e062
0x34b655…2a6f
14 touches
21 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x67905f6e…02a1
0x34b655…2a6f
10 touches
10 conflicts
0xb621e32c…5074
0x34b655…2a6f
10 touches
10 conflicts
0xbf68b5d2…0eba
0x34b655…2a6f
10 touches
10 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0xdfc21d7c53…51e062
Audit this contract →
← previous block·next block →recent activity