← previous blocknext block →recent activity
Analyzing
Block #86,847,906
52 transactions · 46 stateful · 2026-07-10 13:31:00 UTC
Parallelism
73/100
Blocked
70%
Avg conflicts / tx
2.23
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #86,847,906 · 52 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
1w02w04w15w26w07w18w210w111w012w113w214w315w416w517w618w719w820w921w1026w327w131w233w134w337w438w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
12 touches
15 conflicts
0x5fee1ba0…2520
0x34b655…2a6f
12 touches
15 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
12 touches
15 conflicts
0x7da56943…9753
0x34b655…2a6f
12 touches
15 conflicts
0x9f40a209…1193
0x34b655…2a6f
12 touches
15 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity