← previous blocknext block →recent activity
Analyzing
Block #86,836,432
42 transactions · 36 stateful · 2026-07-10 12:14:23 UTC
Parallelism
83/100
Blocked
56%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,836,432 · 42 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
4w05w07w08w110w011w112w213w314w419w120w221w524w127w228w329w431w532w137w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa279b18d…63bc
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x2130a548…c1de
0x34b655…2a6f
8 touches
6 conflicts
0x414ca622…37ab
0x34b655…2a6f
8 touches
6 conflicts
0x574628e9…dcc3
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x3230277c…ef39
0xc8689a…ee79
8 touches
6 conflicts
0x19795ad6…4a16
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
10 conflicts on slot 0xa279b18d93…8363bc
Audit this contract →
← previous block·next block →recent activity