← previous blocknext block →recent activity
Analyzing
Block #86,443,692
37 transactions · 34 stateful · 2026-07-08 16:27:14 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,443,692 · 37 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w29w310w411w512w615w019w124w225w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0xa20a130c…5d59
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x7506443a…4820
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x157dbfb2…4089
0x34b655…2a6f
8 touches
6 conflicts
0xa3e06ffb…6c2b
0x34b655…2a6f
8 touches
6 conflicts
0xb1c67a7d…b9b1
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity