← previous blocknext block →recent activity
Analyzing
Block #85,767,625
17 transactions · 12 stateful · 2026-07-05 13:15:39 UTC
Parallelism
88/100
Blocked
42%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,767,625 · 17 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
1w02w13w06w07w19w114w015w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x418a7b19…b8ca
0x34b655…2a6f
4 touches
1 conflict
0x43e3decb…be40
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0x62d6e82b…a750
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
1 conflict on slot 0x2d071de0f2…94c86e
Audit this contract →
← previous block·next block →recent activity