← previous blocknext block →recent activity
Analyzing
Block #86,633,155
45 transactions · 41 stateful · 2026-07-09 13:35:14 UTC
Parallelism
64/100
Blocked
63%
Avg conflicts / tx
2.4
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #86,633,155 · 45 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
2w03w16w07w18w09w110w211w312w413w514w615w720w221w323w425w227w130w331w442w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
12 touches
15 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
12 touches
15 conflicts
0xa3e06ffb…6c2b
0x34b655…2a6f
12 touches
15 conflicts
0x922c7ebd…6600
0xc8689a…ee79
12 touches
15 conflicts
0x727fbce7…0c80
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity