pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,282,119
← previous block
next block →
recent activity
Analyzing
Block #85,282,119
8 transactions · 7 stateful · 2026-07-03 07:21:26 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,282,119
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x39435dac
· blocks 1
#3
0x5a5d9a99
#4
executeBatch
#5
0xed82b078
#6
setData
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43e2eda1…396f
0x34b655…2a6f
4 touches
1 conflict
0x2406ccf7…c1cb
0x34b655…2a6f
4 touches
1 conflict
0xac61c3cf…cf4f
0x34b655…2a6f
4 touches
1 conflict
0xd31d7e43…0b56
0x34b655…2a6f
4 touches
1 conflict
0x14d04bf5…6c57
0x34b655…2a6f
2 touches
0 conflicts
0x5609b23e…c0a5
0x34b655…2a6f
2 touches
0 conflicts
0x5af10b50…8d5c
0x34b655…2a6f
2 touches
0 conflicts
0x64c8a24d…2887
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
1 conflict on slot
0x43e2eda154…aa396f
Audit this contract →
← previous block
·
next block →
recent activity