pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,846,188
← previous block
next block →
recent activity
Analyzing
Block #93,846,188
14 transactions · 13 stateful · 2026-08-07 06:17:56 UTC
Parallelism
93
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,846,188
· 14 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execOrders
#3
0x5acec890
#4
0x5acec890
#5
execFwdPositionOps
#6
0x3f5c179b
#7
0x29eed2d3
#8
forward
#9
execFwdPositionOps
#10
execFwdPositionOps
#11
commit
#12
0x6a75790c
#13
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x2fe71957…a330
0x34b655…2a6f
2 touches
0 conflicts
0x3a7fb5b5…f0e5
0x34b655…2a6f
2 touches
0 conflicts
0x4755fafb…859b
0x34b655…2a6f
2 touches
0 conflicts
0x4f858307…7642
0x34b655…2a6f
2 touches
0 conflicts
0x513b12c7…47cd
0x34b655…2a6f
2 touches
0 conflicts
0x52b477bc…7ccf
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.
← previous block
·
next block →
recent activity