← previous blocknext block →recent activity
Analyzing
Block #85,194,147
21 transactions · 20 stateful · 2026-07-02 21:35:27 UTC
Parallelism
62/100
Blocked
55%
Avg conflicts / tx
1.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,194,147 · 21 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
1w02w03w15w06w110w211w212w113w315w316w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x85631114…3ff6
0xa6afd3…d132
8 touches
6 conflicts
0x987aeb55…0e2a
0xa6afd3…d132
8 touches
6 conflicts
0x765cd07a…1018
0x34b655…2a6f
6 touches
3 conflicts
0xd63e616b…a07d
0x34b655…2a6f
6 touches
3 conflicts
0xb44564d6…bb43
0x34b655…2a6f
6 touches
3 conflicts
0x6167486f…db40
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity