← previous blocknext block →recent activity
Analyzing
Block #85,856,080
12 transactions · 9 stateful · 2026-07-05 23:04:54 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,856,080 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6637e421…af93
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
4 touches
1 conflict
0x8fbde2b3…9b8f
0x34b655…2a6f
4 touches
1 conflict
0xa72fd366…c5f8
0x34b655…2a6f
4 touches
1 conflict
0xded5ec0c…f0fc
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xe5e7089a…fb91
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 0x6637e421bf…b0af93
Audit this contract →
← previous block·next block →recent activity