← previous blocknext block →recent activity
Analyzing
Block #86,055,018
28 transactions · 25 stateful · 2026-07-06 21:12:05 UTC
Parallelism
71/100
Blocked
32%
Avg conflicts / tx
0.61
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,055,018 · 28 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
1w04w05w18w115w216w322w423w524w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xfed09e59…a493
0x34b655…2a6f
8 touches
6 conflicts
0x231ccc13…a7c6
0x34b655…2a6f
6 touches
3 conflicts
0xcc25f1e5…2cac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x10326aa1…38a3
0x34b655…2a6f
4 touches
1 conflict
0x1416e2fb…e2b3
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity