pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,101,519
← previous block
next block →
recent activity
Analyzing
Block #85,101,519
10 transactions · 9 stateful · 2026-07-02 11:17:22 UTC
Parallelism
60
/100
Blocked
33
%
Avg conflicts / tx
0.5
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,101,519
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
0x5a5d9a99
· blocks 2
#4
setData
#7
execOrders
#9
0xc7e3ec2c
#5
execOrders
· blocks 2
#6
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w2
8
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4f2daaf7…f9e7
0x34b655…2a6f
6 touches
3 conflicts
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0xbbb9fa77…d121
0x34b655…2a6f
4 touches
1 conflict
0x20cd811f…514c
0x34b655…2a6f
4 touches
1 conflict
0xbaeed020…92f8
0x34b655…2a6f
4 touches
1 conflict
0x75ae301b…a58b
0x34b655…2a6f
4 touches
1 conflict
0xbc2d1037…ff1a
0x40c49f…2af0
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
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity