pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,149,507
← previous block
next block →
recent activity
Analyzing
Block #93,149,507
7 transactions · 7 stateful · 2026-08-04 19:55:25 UTC
Parallelism
29
/100
Blocked
57
%
Avg conflicts / tx
0.86
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,149,507
· 7 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
execOrders
· blocks 2
#4
updateDataFeedsValuesPartial
#2
execOrders
· blocks 1
#3
execFwdPositionOps
· blocks 2
#5
execOrders
· blocks 1
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
5
w3
6
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xb5a3b1be…8122
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf4e39093…f750
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
0x5500f593…a813
0x34b655…2a6f
4 touches
1 conflict
0x8a1db511…3ac9
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
0xf3d10975b0…050d07
Audit this contract →
← previous block
·
next block →
recent activity