← previous blocknext block →recent activity
Analyzing
Block #87,711,806
78 transactions · 52 stateful · 2026-07-14 13:48:07 UTC
Parallelism
82/100
Blocked
67%
Avg conflicts / tx
1.64
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,711,806 · 78 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
1w02w13w04w15w06w115w216w125w227w228w331w032w141w042w143w244w345w455w357w458w362w565w466w267w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf78ee7f…e7fd
0x34b655…2a6f
18 touches
36 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x307414a5…7214
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 0xbf78ee7fb5…b5e7fd
Audit this contract →
← previous block·next block →recent activity