pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,244,813
← previous block
next block →
recent activity
Analyzing
Block #95,244,813
10 transactions · 8 stateful · 2026-08-12 03:52:05 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,244,813
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#2
execPerpOps
#3
execPerpOps
#5
execFwdPositionOps
#6
0x222d4ad6
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x59558d29
#4
execFwdPositionOps
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
0x7be3246e…f89f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…001c
0x1122a5…6e92
2 touches
0 conflicts
0x34cdb3c2…96d2
0x34b655…2a6f
2 touches
0 conflicts
0x37d710c8…45c1
0x34b655…2a6f
2 touches
0 conflicts
0x3f4f9f22…8ad6
0x34b655…2a6f
2 touches
0 conflicts
0x3f4f9f22…8ad7
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
0x7be3246e43…72f89f
Audit this contract →
← previous block
·
next block →
recent activity