pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,597,803
← previous block
next block →
recent activity
Analyzing
Block #85,597,803
11 transactions · 9 stateful · 2026-07-04 18:23:44 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,597,803
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0x6a495028
#3
artefact_keep
#4
execFwdPositionOps
· blocks 1
#5
0x3f5c179b
#7
updateDataFeedsValuesPartial
#8
0x6a495028
#9
setData
#10
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94e7f277…471b
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
0x34b655…2a6f
4 touches
1 conflict
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0xe956cfaa…215a
0x34b655…2a6f
4 touches
1 conflict
0x287d281e…bdc1
0x34b655…2a6f
4 touches
1 conflict
0x71a9ccf8…4adf
0x34b655…2a6f
3 touches
1 conflict
0xd8fd2add…50fc
0x69df8a…6292
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
0x94e7f27794…c6471b
Audit this contract →
← previous block
·
next block →
recent activity