pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,275,873
← previous block
next block →
recent activity
Analyzing
Block #85,275,873
9 transactions · 8 stateful · 2026-07-03 06:39:52 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,275,873
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 2
#5
0x3f5c179b
#7
createGame
#8
setData
#4
0x0f6795d9
· blocks 1
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x624e3c40…6d56
0x34b655…2a6f
4 touches
1 conflict
0xe1791476…927a
0x34b655…2a6f
4 touches
1 conflict
0x14f6fe51…1c24
0x34b655…2a6f
2 touches
0 conflicts
0x21d22421…0b7a
0x34b655…2a6f
2 touches
0 conflicts
0x225c3858…2a9b
0x34b655…2a6f
2 touches
0 conflicts
0x43e2eda1…396f
0x34b655…2a6f
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
3 conflicts on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity