← previous blocknext block →recent activity
Analyzing
Block #85,178,783
52 transactions · 38 stateful · 2026-07-02 19:53:10 UTC
Parallelism
64/100
Blocked
79%
Avg conflicts / tx
3.77
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #85,178,783 · 52 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
1w02w15w26w07w18w211w314w315w016w124w025w126w227w328w429w530w631w742w245w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
34 touches
136 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
20 touches
45 conflicts
0x05a7428b…ddf3
0x34b655…2a6f
16 touches
28 conflicts
0x922c7ebd…6600
0xc8689a…ee79
14 touches
21 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
14 touches
21 conflicts
0x51a914cf…a822
0x34b655…2a6f
14 touches
21 conflicts
0x548145a9…cfce
0x34b655…2a6f
14 touches
21 conflicts
0x5ad3280d…16bb
0x34b655…2a6f
14 touches
21 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
136 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity