pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,928,124
← previous block
next block →
recent activity
Analyzing
Block #93,928,124
11 transactions · 10 stateful · 2026-08-07 13:10:19 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,928,124
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
execOrder
· blocks 1
#4
withdraw
#5
execFwdPositionOps
· blocks 1
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#10
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d5fc820…1750
0x34b655…2a6f
4 touches
1 conflict
0x1438d03e…4250
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4f394483…ff62
0x34b655…2a6f
4 touches
1 conflict
0x10a0e8ee…ac08
0x34b655…2a6f
2 touches
0 conflicts
0x10e77cb1…d08b
0x34b655…2a6f
2 touches
0 conflicts
0x41377979…0a18
0x34b655…2a6f
2 touches
0 conflicts
0x58b6dfdc…67c8
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
0x8d5fc820e4…ea1750
Audit this contract →
← previous block
·
next block →
recent activity