pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,719,586
← previous block
next block →
recent activity
Analyzing
Block #94,719,586
11 transactions · 10 stateful · 2026-08-10 07:47:02 UTC
Parallelism
82
/100
Blocked
30
%
Avg conflicts / tx
0.36
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,719,586
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
execOrders
· blocks 1
#3
execOrder
· blocks 2
#5
0x5acec890
#7
updateDataFeedsValuesPartial
#8
transfer
#9
setData
· blocks 1
#4
execOrder
#6
execFwdPositionOps
#10
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
6
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70cfbacf…5c46
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x917f99a5…7989
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xfb24441a…4183
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x379dc435…6616
0x34b655…2a6f
4 touches
1 conflict
0x5c16527f…628c
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
1 conflict on slot
0x70cfbacfa4…e85c46
Audit this contract →
← previous block
·
next block →
recent activity