← previous blocknext block →recent activity
Analyzing
Block #85,631,215
11 transactions · 11 stateful · 2026-07-04 22:06:09 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,631,215 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd8d502…d359
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9ee980b7…60c5
0x5afd3e…7620
4 touches
1 conflict
0xf720e696…d004
0x5afd3e…7620
4 touches
1 conflict
0x4b8261ba…1eac
0xd32edf…ff58
3 touches
1 conflict
0x116c6b2f…b15d
0x065c9d…c394
2 touches
0 conflicts
0x209f1d6c…c068
0x065c9d…c394
2 touches
0 conflicts
0x54d1f1ee…681f
0x065c9d…c394
2 touches
0 conflicts
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
1 conflict on slot 0xafd8d502ad…46d359
Audit this contract →
← previous block·next block →recent activity