pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,133,108
← previous block
next block →
recent activity
Analyzing
Block #85,133,108
9 transactions · 6 stateful · 2026-07-02 14:48:56 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,133,108
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a467ad0
#2
0x5a5d9a99
· blocks 1
#3
0x6a467ad0
#5
updateDataFeedsValuesPartial
#6
0x6a467ad0
#7
setData
#8
0xc7e3ec2c
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58603063…4ef0
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x014b5557…6ef1
0x34b655…2a6f
2 touches
0 conflicts
0x022b49db…a477
0x34b655…2a6f
2 touches
0 conflicts
0x1275ec6e…0bbb
0x34b655…2a6f
2 touches
0 conflicts
0x12f1cd03…426b
0x34b655…2a6f
2 touches
0 conflicts
0x169de76a…271b
0x34b655…2a6f
2 touches
0 conflicts
0x25e3730b…24a9
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
0x586030638f…0d4ef0
Audit this contract →
← previous block
·
next block →
recent activity