← previous blocknext block →recent activity
Analyzing
Block #85,616,901
16 transactions · 14 stateful · 2026-07-04 20:30:50 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,616,901 · 16 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
1w02w13w24w07w08w112w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64c57c87…5e42
0x34b655…2a6f
8 touches
6 conflicts
0x97c67486…27fe
0x34b655…2a6f
6 touches
3 conflicts
0xa75d0292…4db1
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xe732567d…b65d
0x34b655…2a6f
6 touches
3 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
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
6 conflicts on slot 0x64c57c87ad…425e42
Audit this contract →
← previous block·next block →recent activity