pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,374,974
← previous block
next block →
recent activity
Analyzing
Block #95,374,974
10 transactions · 10 stateful · 2026-08-12 14:57:59 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,374,974
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6bdec372
#2
0xab083028
#3
execOrders
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#7
setData
#8
0x59558d29
#9
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67a56c8b…f955
0x34b655…2a6f
4 touches
1 conflict
0xbcab7dbe…2825
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xebc2e0d7…958e
0x3bd359…433a
2 touches
0 conflicts
0x0d33c3de…4207
0x754704…b603
2 touches
0 conflicts
0x9194f4a3…10b8
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
0x67a56c8b2e…d7f955
Audit this contract →
← previous block
·
next block →
recent activity