← previous blocknext block →recent activity
Analyzing
Block #85,663,311
11 transactions · 11 stateful · 2026-07-05 01:39:48 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,663,311 · 11 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
1w02w13w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ee31890…df58
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xda2ee2e7…968a
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x15629a48…418c
0x40c49f…2af0
2 touches
0 conflicts
0x402599c8…ac4c
0x40c49f…2af0
2 touches
0 conflicts
0x5602982a…0054
0x40c49f…2af0
2 touches
0 conflicts
0xb180ac82…0e96
0x40c49f…2af0
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
1 conflict on slot 0x9ee3189089…d3df58
Audit this contract →
← previous block·next block →recent activity