pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,553,820
← previous block
next block →
recent activity
Analyzing
Block #93,553,820
11 transactions · 8 stateful · 2026-08-06 05:48:08 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,553,820
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
execute
#5
execFwdPositionOps
· blocks 1
#6
0x3f5c179b
#8
execFwdPositionOps
#9
0x6a74208f
#10
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1e302fd3…642c
0x34b655…2a6f
2 touches
0 conflicts
0x3f5f366d…10d9
0x34b655…2a6f
2 touches
0 conflicts
0x481b500f…7ef3
0x34b655…2a6f
2 touches
0 conflicts
0x4b7e216a…7258
0x34b655…2a6f
2 touches
0 conflicts
0x4b7e216a…7259
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity