pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,149,716
← previous block
next block →
recent activity
Analyzing
Block #93,149,716
10 transactions · 9 stateful · 2026-08-04 19:56:28 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,149,716
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x3f5c179b
#3
executeBatch
#4
0x0f6795d9
· blocks 2
#5
0x94defb17
· blocks 1
#9
setData
#6
0x94defb17
#7
0x0f6795d9
· blocks 1
#8
0x0f6795d9
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
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb35da893…75cc
0x968279…9342
4 touches
1 conflict
0x07e0e754…35cc
0x968279…9342
4 touches
1 conflict
0x07e0e754…35ce
0x968279…9342
4 touches
1 conflict
0xb35da893…75c9
0x968279…9342
4 touches
1 conflict
0xb35da893…75ca
0x968279…9342
4 touches
1 conflict
0x1cdfe548…d3aa
0x34b655…2a6f
4 touches
1 conflict
0x3d158563…8713
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity