pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,160,020
← previous block
next block →
recent activity
Analyzing
Block #95,160,020
11 transactions · 10 stateful · 2026-08-11 20:44:43 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,160,020
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
0x3f5c179b
#6
execFwdPositionOps
#7
forward
#8
execOrders
#9
0x6a7b8a33
#10
setData
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5419303…8d89
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0ddfdaf2…9e00
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x044844a0…7418
0x34b655…2a6f
2 touches
0 conflicts
0x093e48d5…f000
0x34b655…2a6f
2 touches
0 conflicts
0x28e312da…2a2a
0x34b655…2a6f
2 touches
0 conflicts
0x35d95fb0…db9e
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
0xa541930306…eb8d89
Audit this contract →
← previous block
·
next block →
recent activity