pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,537,911
← previous block
next block →
recent activity
Analyzing
Block #93,537,911
10 transactions · 8 stateful · 2026-08-06 04:28:09 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,537,911
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
placeAndExecuteMarketBuy
#6
0x3f5c179b
· blocks 1
#8
execFwdPositionOps
#9
setData
#7
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x134411c7…4619
0x851145…3f07
4 touches
1 conflict
0xb7729c24…9f17
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
2 touches
0 conflicts
0x3a2a8323…3f40
0x34b655…2a6f
2 touches
0 conflicts
0x3b3e5f00…9a88
0x34b655…2a6f
2 touches
0 conflicts
0x47ee9f76…8dee
0x34b655…2a6f
2 touches
0 conflicts
0x47ee9f76…8def
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:
0x851145ea…9f3f07
1 conflict on slot
0x134411c750…de4619
Audit this contract →
← previous block
·
next block →
recent activity