← previous blocknext block →recent activity
Analyzing
Block #85,144,416
13 transactions · 13 stateful · 2026-07-02 16:04:23 UTC
Parallelism
54/100
Blocked
54%
Avg conflicts / tx
1.23
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,144,416 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w06w17w19w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43e2eda1…396f
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x4b5be307…0a25
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x81888fb0…2313
0x34b655…2a6f
6 touches
3 conflicts
0x3e1c3586…83d7
0xa6afd3…d132
4 touches
1 conflict
0x11bfda5f…1b5c
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 0x43e2eda154…aa396f
Audit this contract →
← previous block·next block →recent activity