← previous blocknext block →recent activity
Analyzing
Block #87,704,908
25 transactions · 21 stateful · 2026-07-14 13:01:56 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,704,908 · 25 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
2w04w07w111w112w213w014w115w216w320w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0001
0xc1ff9f…b0fc
6 touches
3 conflicts
0xab5ba139…ea6f
0x34b655…2a6f
6 touches
3 conflicts
0xb5c4826d…bdd6
0x2b46c0…1669
4 touches
1 conflict
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x2754c3f9…9863
0x34b655…2a6f
4 touches
1 conflict
0x51d2f633…e7f5
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity