← previous blocknext block →recent activity
Analyzing
Block #85,668,789
17 transactions · 15 stateful · 2026-07-05 02:16:15 UTC
Parallelism
65/100
Blocked
33%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,668,789 · 17 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
4w05w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1aaf4996…65ec
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0x84826d4d…fd18
0x34b655…2a6f
4 touches
1 conflict
0x99479bc5…3a88
0x34b655…2a6f
4 touches
1 conflict
0xf1dab3b8…1ab6
0x34b655…2a6f
4 touches
1 conflict
0xf5d82021…006d
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
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 0x1aaf499609…4665ec
Audit this contract →
← previous block·next block →recent activity