pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,537,902
← previous block
next block →
recent activity
Analyzing
Block #85,537,902
8 transactions · 8 stateful · 2026-07-04 11:44:45 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,537,902
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
executeBatch
#3
0x3f5c179b
#5
0xed82b078
#6
updateDataFeedsValuesPartial
#7
setData
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x828cefbb…7934
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x517d35c7…f359
0x34b655…2a6f
2 touches
0 conflicts
0x66d88b03…0443
0x34b655…2a6f
2 touches
0 conflicts
0xc730f733…d462
0x34b655…2a6f
2 touches
0 conflicts
0x09a15b10…2639
0x754704…b603
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
0x9a3068dd84…9918f1
Audit this contract →
← previous block
·
next block →
recent activity