← previous blocknext block →recent activity
Analyzing
Block #87,713,919
56 transactions · 42 stateful · 2026-07-14 14:02:16 UTC
Parallelism
73/100
Blocked
50%
Avg conflicts / tx
1.73
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,713,919 · 56 txs across 15 waves · depth 15
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
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w08w19w213w014w015w116w223w024w125w226w327w428w529w630w731w832w936w1043w346w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
14 touches
21 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0xe3f2706b…d3ec
0x34b655…2a6f
8 touches
6 conflicts
0xc30f2923…382c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x14e835ba…9463
0xd32edf…ff58
7 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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity