← previous blocknext block →recent activity
Analyzing
Block #86,836,345
50 transactions · 39 stateful · 2026-07-10 12:13:48 UTC
Parallelism
74/100
Blocked
64%
Avg conflicts / tx
2.08
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #86,836,345 · 50 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w08w111w012w113w218w220w021w122w223w225w326w427w528w629w730w831w932w1036w337w343w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0x2b268fa9…eba2
0x34b655…2a6f
16 touches
28 conflicts
0xf94d24c1…5f81
0x34b655…2a6f
16 touches
28 conflicts
0xa07e7b13…7513
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
16 touches
28 conflicts
0xbb96f8af…205f
0x34b655…2a6f
16 touches
28 conflicts
0xeb9f299d…5df5
0x34b655…2a6f
16 touches
28 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