← previous blocknext block →recent activity
Analyzing
Block #87,589,765
19 transactions · 18 stateful · 2026-07-14 00:12:02 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.16
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,589,765 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w28w39w410w011w112w215w318w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6b89ebb…a66e
0x34b655…2a6f
12 touches
15 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
10 touches
10 conflicts
0xde7dc8d8…1ccf
0x34b655…2a6f
10 touches
10 conflicts
0x34d95d94…3a16
0x34b655…2a6f
10 touches
10 conflicts
0x67905f6e…02a1
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x201679bc…0414
0x34b655…2a6f
10 touches
10 conflicts
0x875164c2…f8a2
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
15 conflicts on slot 0xa6b89ebbaf…5fa66e
Audit this contract →
← previous block·next block →recent activity