pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,599,179
← previous block
next block →
recent activity
Analyzing
Block #95,599,179
11 transactions · 9 stateful · 2026-08-13 09:47:10 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,599,179
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x45b7e41f
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
executeBatch
· blocks 1
#8
setData
#9
0x59558d29
#10
execOrders
#6
executeBatch
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc5fc032…8d7e
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xbc5fc032…8d7d
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xd9d0b0b5…32f5
0x34b655…2a6f
3 touches
1 conflict
0x528c3265…cbb1
0xe52b14…7230
3 touches
1 conflict
0x3e5b464f…0360
0x34b655…2a6f
3 touches
1 conflict
0xaa2f6971…c549
0xea1b8e…c5ec
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
0xbc5fc032c1…c78d7e
Audit this contract →
← previous block
·
next block →
recent activity