← previous blocknext block →recent activity
Analyzing
Block #87,718,082
40 transactions · 36 stateful · 2026-07-14 14:30:16 UTC
Parallelism
65/100
Blocked
67%
Avg conflicts / tx
2.35
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,718,082 · 40 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
1w02w04w17w08w110w111w012w113w014w115w216w317w418w519w620w721w823w225w529w630w231w234w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x7525206c…fbd5
0x34b655…2a6f
12 touches
15 conflicts
0xb2ebdaaa…8845
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x67905f6e…02a1
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x13510de3…1c68
0x34b655…2a6f
8 touches
6 conflicts
0x5bf44783…6166
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity