pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,399,090
← previous block
next block →
recent activity
Analyzing
Block #93,399,090
12 transactions · 12 stateful · 2026-08-05 16:50:17 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,399,090
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
execFwdPositionOps
· blocks 1
#5
0x3f5c179b
#6
forward
#7
0xc0c16b76
#8
execFwdPositionOps
#9
setData
#11
0x59558d29
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6460413e…bc36
0x34b655…2a6f
4 touches
1 conflict
0x5f56ffe5…09c0
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x14eb2f47…8a2e
0x34b655…2a6f
2 touches
0 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
2 touches
0 conflicts
0x21f49676…6f7e
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x7c1d804e…835c
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
0x6460413e86…88bc36
Audit this contract →
← previous block
·
next block →
recent activity