← previous blocknext block →recent activity
Analyzing
Block #85,130,247
14 transactions · 13 stateful · 2026-07-02 14:29:48 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,130,247 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fffd49d…772a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5efea426…3d66
0x34b655…2a6f
6 touches
3 conflicts
0x198a5916…44c1
0x34b655…2a6f
4 touches
1 conflict
0x7c3bb16b…101d
0x34b655…2a6f
4 touches
1 conflict
0x264f7d7d…8444
0x34b655…2a6f
4 touches
1 conflict
0x2697123c…8526
0x34b655…2a6f
4 touches
1 conflict
0x3fde350e…8d43
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 0x7fffd49db6…f8772a
Audit this contract →
← previous block·next block →recent activity