← previous blocknext block →recent activity
Analyzing
Block #85,136,215
23 transactions · 21 stateful · 2026-07-02 15:09:40 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,136,215 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w18w29w010w111w212w313w416w221w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06040b44…e244
0x34b655…2a6f
10 touches
10 conflicts
0x7506443a…4820
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x64cdbccd…1c59
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0xe47478a3…a058
0x34b655…2a6f
8 touches
6 conflicts
0xd3ef5630…0de9
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
10 conflicts on slot 0x06040b44e2…0de244
Audit this contract →
← previous block·next block →recent activity