← previous blocknext block →recent activity
Analyzing
Block #85,504,490
23 transactions · 19 stateful · 2026-07-04 08:02:22 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,504,490 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w19w010w011w112w114w217w018w219w320w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xb838bbe6…2931
0x34b655…2a6f
6 touches
3 conflicts
0x830b63a6…8105
0x34b655…2a6f
6 touches
3 conflicts
0xf357ed8b…e65c
0x34b655…2a6f
6 touches
3 conflicts
0x5dd1f5d4…deac
0x34b655…2a6f
6 touches
3 conflicts
0x6fb2976f…64eb
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity