pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,222,378
← previous block
next block →
recent activity
Analyzing
Block #85,222,378
9 transactions · 7 stateful · 2026-07-03 00:43:30 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,222,378
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
removeLiquidityNATIVE
#5
0x0f6795d9
#6
0x0f6795d9
#8
setData
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5310ef7…485a
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xd16df6cd…5532
0x40c49f…2af0
4 touches
1 conflict
0xf4e246c1…030a
0x40c49f…2af0
3 touches
1 conflict
0xb5b1684b…b727
0x40c49f…2af0
3 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0xa22b3a57…5bce
0x40c49f…2af0
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
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:
0x40c49f17…d22af0
1 conflict on slot
0xf5310ef780…e2485a
Audit this contract →
← previous block
·
next block →
recent activity