← previous blocknext block →recent activity
Analyzing
Block #85,610,146
8 transactions · 7 stateful · 2026-07-04 19:45:55 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,610,146 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fe7e126…6dd2
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xa49449e1…3460
0x34b655…2a6f
4 touches
1 conflict
0x0ff91e5e…6434
0x34b655…2a6f
4 touches
1 conflict
0x2d605961…113f
0x34b655…2a6f
4 touches
1 conflict
0xe82f668c…b952
0x34b655…2a6f
4 touches
1 conflict
0xcb05bed1…f155
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
3 conflicts on slot 0x5fe7e1267e…896dd2
Audit this contract →
← previous block·next block →recent activity