pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,767,820
← previous block
next block →
recent activity
Analyzing
Block #92,767,820
11 transactions · 11 stateful · 2026-08-03 11:53:47 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,767,820
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
permit2TransferAndMulticall
#5
execFwdPositionOps
· blocks 1
#6
0x94defb17
· blocks 1
#9
transfer
#10
0x59558d29
#7
0x94defb17
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf36b90da…1416
0x968279…9342
4 touches
1 conflict
0xea5b160f…738a
0x968279…9342
4 touches
1 conflict
0xea5b160f…738b
0x968279…9342
4 touches
1 conflict
0xea5b160f…738e
0x968279…9342
4 touches
1 conflict
0xea5b160f…738f
0x968279…9342
4 touches
1 conflict
0xea5b160f…7391
0x968279…9342
4 touches
1 conflict
0xf36b90da…1413
0x968279…9342
4 touches
1 conflict
0xf36b90da…1414
0x968279…9342
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:
0x96827978…f09342
1 conflict on slot
0xf36b90da9b…da1416
Audit this contract →
← previous block
·
next block →
recent activity