← previous blocknext block →recent activity
Analyzing
Block #86,788,504
42 transactions · 33 stateful · 2026-07-10 06:53:54 UTC
Parallelism
76/100
Blocked
70%
Avg conflicts / tx
1.83
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,788,504 · 42 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w28w39w410w511w613w714w835w836w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3688185…9b36
0x34b655…2a6f
16 touches
28 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
14 touches
21 conflicts
0xb4c35fcd…43ae
0xa6afd3…d132
14 touches
21 conflicts
0x89750670…2dea
0xa6afd3…d132
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
14 touches
21 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
14 touches
21 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
12 touches
15 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
28 conflicts on slot 0xc36881859a…c49b36
Audit this contract →
← previous block·next block →recent activity