← previous blocknext block →recent activity
Analyzing
Block #85,173,886
44 transactions · 41 stateful · 2026-07-02 19:20:30 UTC
Parallelism
68/100
Blocked
71%
Avg conflicts / tx
2.68
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #85,173,886 · 44 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w27w08w110w213w014w115w216w317w418w519w620w721w822w923w1024w1126w328w129w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0x922c7ebd…6600
0xc8689a…ee79
16 touches
28 conflicts
0x16b3a441…13db
0x34b655…2a6f
16 touches
28 conflicts
0x51a914cf…a822
0x34b655…2a6f
16 touches
28 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
16 touches
28 conflicts
0xa457c06e…2f06
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x30dae839…7160
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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity