← previous blocknext block →recent activity
Analyzing
Block #87,754,254
44 transactions · 41 stateful · 2026-07-14 18:32:14 UTC
Parallelism
66/100
Blocked
68%
Avg conflicts / tx
2.89
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,754,254 · 44 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
1w02w04w16w07w18w09w110w012w113w214w315w116w217w318w419w520w621w722w823w932w333w436w637w139w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
26 touches
78 conflicts
0x644919d7…9727
0x34b655…2a6f
12 touches
15 conflicts
0x2f461725…5ab2
0x34b655…2a6f
10 touches
10 conflicts
0x70b90757…51be
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
10 touches
10 conflicts
0x388633a0…86cd
0x34b655…2a6f
10 touches
10 conflicts
0x9ae859db…2d84
0x34b655…2a6f
8 touches
6 conflicts
0x9fd37234…2731
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
78 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity