← previous blocknext block →recent activity
Analyzing
Block #87,355,270
34 transactions · 28 stateful · 2026-07-12 22:02:58 UTC
Parallelism
53/100
Blocked
68%
Avg conflicts / tx
2.68
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,355,270 · 34 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
2w03w14w06w110w011w112w213w314w415w516w617w718w819w920w1022w523w1124w226w1227w1333w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0x321eac33…6aca
0x34b655…2a6f
10 touches
10 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
10 touches
10 conflicts
0x3662953b…09bd
0x34b655…2a6f
10 touches
10 conflicts
0x636fd21a…9978
0x34b655…2a6f
10 touches
10 conflicts
0x63c900f4…2600
0x34b655…2a6f
10 touches
10 conflicts
0x727fbce7…0c80
0x34b655…2a6f
10 touches
10 conflicts
0x7506443a…4820
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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity