← previous blocknext block →recent activity
Analyzing
Block #86,708,892
38 transactions · 33 stateful · 2026-07-09 22:02:04 UTC
Parallelism
58/100
Blocked
73%
Avg conflicts / tx
2.71
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #86,708,892 · 38 txs across 16 waves · depth 16
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
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w310w011w112w213w314w415w516w617w718w819w920w1021w1122w529w330w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
22 touches
55 conflicts
0x1535d171…c68b
0x34b655…2a6f
12 touches
15 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
12 touches
15 conflicts
0x85c84f98…06d7
0x34b655…2a6f
10 touches
10 conflicts
0x64a785e4…0110
0x34b655…2a6f
10 touches
10 conflicts
0xf58f4849…c7c7
0x34b655…2a6f
10 touches
10 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
10 touches
10 conflicts
0xa5ab7b8a…c97b
0x34b655…2a6f
10 touches
10 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
55 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity