← previous blocknext block →recent activity
Analyzing
Block #85,678,905
23 transactions · 21 stateful · 2026-07-05 03:23:35 UTC
Parallelism
78/100
Blocked
57%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,678,905 · 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
1w02w14w05w16w07w110w211w212w113w314w416w019w120w221w322w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1aaf4996…65ec
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xbe4569ad…2ffb
0x065c9d…c394
6 touches
3 conflicts
0xb68e226d…c054
0xa6afd3…d132
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x3181bd2d…cf15
0xa6afd3…d132
6 touches
3 conflicts
0xc4cb048e…7562
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x1aaf499609…4665ec
Audit this contract →
← previous block·next block →recent activity