← previous blocknext block →recent activity
Analyzing
Block #87,705,641
57 transactions · 44 stateful · 2026-07-14 13:06:52 UTC
Parallelism
70/100
Blocked
66%
Avg conflicts / tx
2.23
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,705,641 · 57 txs across 17 waves · depth 17
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
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w39w010w111w222w023w124w225w326w427w528w629w730w831w941w344w446w547w449w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
26 touches
78 conflicts
0x5170a218…3a84
0xc8689a…ee79
12 touches
15 conflicts
0x5ec64628…72e4
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0xad0c7701…1d83
0x34b655…2a6f
8 touches
6 conflicts
0xee4fe1f7…3ead
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0xb538c6fa…9aea
0x1b6862…e19c
6 touches
3 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
78 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity