← previous blocknext block →recent activity
Analyzing
Block #86,663,938
36 transactions · 33 stateful · 2026-07-09 17:02:06 UTC
Parallelism
47/100
Blocked
67%
Avg conflicts / tx
2.19
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #86,663,938 · 36 txs across 19 waves · depth 19
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
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w18w09w110w211w312w413w514w616w817w918w1022w1224w1326w134w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x12573732…e891
0x34b655…2a6f
14 touches
21 conflicts
0x922c7ebd…6600
0xc8689a…ee79
14 touches
21 conflicts
0xf58f4849…c7c7
0x34b655…2a6f
14 touches
21 conflicts
0x548145a9…cfce
0x34b655…2a6f
14 touches
21 conflicts
0x727fbce7…0c80
0x34b655…2a6f
14 touches
21 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
12 touches
15 conflicts
0x87f3dc22…eb64
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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity