← previous blocknext block →recent activity
Analyzing
Block #85,123,443
43 transactions · 34 stateful · 2026-07-02 13:44:19 UTC
Parallelism
56/100
Blocked
74%
Avg conflicts / tx
2.72
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #85,123,443 · 43 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
1w04w15w26w315w016w117w218w319w420w521w622w723w824w925w1026w1127w1232w233w135w436w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
14 touches
21 conflicts
0xe47478a3…a058
0x34b655…2a6f
14 touches
21 conflicts
0x40b5f387…a164
0x34b655…2a6f
14 touches
21 conflicts
0x63b15849…80b2
0x34b655…2a6f
14 touches
21 conflicts
0x922c7ebd…6600
0xc8689a…ee79
14 touches
21 conflicts
0x548145a9…cfce
0x34b655…2a6f
14 touches
21 conflicts
0x4384dd01…4f99
0x34b655…2a6f
13 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
78 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity