← previous blocknext block →recent activity
Analyzing
Block #87,713,440
20 transactions · 19 stateful · 2026-07-14 13:59:02 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,713,440 · 20 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
3w04w15w06w17w28w39w410w513w014w115w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x0ba865dd…a249
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x5cf7c7d2…9640
0x34b655…2a6f
8 touches
6 conflicts
0x5ec64628…72e4
0x34b655…2a6f
8 touches
6 conflicts
0x720553e3…183c
0x34b655…2a6f
8 touches
6 conflicts
0x74fd0a9b…3aaa
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity