pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,181,244
← previous block
next block →
recent activity
Analyzing
Block #95,181,244
11 transactions · 10 stateful · 2026-08-11 22:31:28 UTC
Parallelism
73
/100
Blocked
30
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,181,244
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrder
· blocks 2
#3
updateDataFeedsValuesPartial
#5
executeBatch
#6
execFwdPositionOps
#7
0x6a7ba338
#8
transfer
· blocks 1
#10
setData
#2
execOrder
· blocks 1
#9
transfer
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4268cc8…dc39
0x34b655…2a6f
6 touches
3 conflicts
0xea3b49a7…24d7
0x34b655…2a6f
6 touches
3 conflicts
0xdbb9cf89…166c
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x443f8ead…a752
0x34b655…2a6f
5 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x5e8223c2…c242
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
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
0xf4268cc8b9…24dc39
Audit this contract →
← previous block
·
next block →
recent activity