← previous blocknext block →recent activity
Analyzing
Block #85,275,405
13 transactions · 13 stateful · 2026-07-03 06:36:46 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,275,405 · 13 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
1w02w14w05w28w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c233126…0be7
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x1c25cccc…bb41
0x34b655…2a6f
6 touches
3 conflicts
0x43e2eda1…396f
0x34b655…2a6f
6 touches
3 conflicts
0x7f2e06a0…7d82
0x065c9d…c394
4 touches
1 conflict
0x3a4ac642…d0b3
0x34b655…2a6f
4 touches
1 conflict
0x2697123c…8526
0x34b655…2a6f
4 touches
1 conflict
0xa62c47db…5ec8
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
3 conflicts on slot 0x9c2331261e…fa0be7
Audit this contract →
← previous block·next block →recent activity