← previous blocknext block →recent activity
Analyzing
Block #85,123,372
28 transactions · 26 stateful · 2026-07-02 13:43:51 UTC
Parallelism
71/100
Blocked
46%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,123,372 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x548145a9…cfce
0x34b655…2a6f
16 touches
28 conflicts
0x63b15849…80b2
0x34b655…2a6f
16 touches
28 conflicts
0x922c7ebd…6600
0xc8689a…ee79
16 touches
28 conflicts
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0xe47478a3…a058
0x34b655…2a6f
16 touches
28 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
16 touches
28 conflicts
0x4384dd01…4f99
0x34b655…2a6f
16 touches
28 conflicts
0xc5e88bf9…3817
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
28 conflicts on slot 0x548145a9ab…abcfce
Audit this contract →
← previous block·next block →recent activity