← previous blocknext block →recent activity
Analyzing
Block #86,904,613
36 transactions · 29 stateful · 2026-07-10 19:50:15 UTC
Parallelism
50/100
Blocked
72%
Avg conflicts / tx
2.69
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #86,904,613 · 36 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w08w09w110w211w312w413w514w615w716w819w920w1021w1123w124w128w1029w1130w1233w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
10 touches
10 conflicts
0x7babfe9a…ff96
0x34b655…2a6f
10 touches
10 conflicts
0x5a19ef35…dc70
0x34b655…2a6f
8 touches
6 conflicts
0x9138a113…0d5f
0x34b655…2a6f
8 touches
6 conflicts
0x94710b77…a921
0x34b655…2a6f
8 touches
6 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