pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,526,351
← previous block
next block →
recent activity
Analyzing
Block #85,526,351
10 transactions · 10 stateful · 2026-07-04 10:27:52 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,526,351
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x6a48e09f
#4
0x5a5d9a99
#5
0x3f5c179b
#6
0xed82b078
#7
0x0f6795d9
· blocks 1
#8
setData
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2697123c…8526
0x34b655…2a6f
4 touches
1 conflict
0xda2ee2e7…968a
0x34b655…2a6f
4 touches
1 conflict
0x95934af8…8190
0x34b655…2a6f
4 touches
1 conflict
0x011d8099…2473
0x34b655…2a6f
2 touches
0 conflicts
0x184cafae…fb7d
0x34b655…2a6f
2 touches
0 conflicts
0x3923cd2c…e6d3
0x34b655…2a6f
2 touches
0 conflicts
0x513a16ac…f8ed
0x34b655…2a6f
2 touches
0 conflicts
0x8510eda1…e037
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
0x2697123ce4…5e8526
Audit this contract →
← previous block
·
next block →
recent activity