pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,064,511
← previous block
next block →
recent activity
Analyzing
Block #93,064,511
11 transactions · 11 stateful · 2026-08-04 12:46:45 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,064,511
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
execFwdPositionOps
#3
0x3f5c179b
· blocks 1
#5
forward
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x6a71dfac
#9
setData
#10
0xc7e3ec2c
#4
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x06b4e86e…b0a0
0x34b655…2a6f
2 touches
0 conflicts
0x06d13840…23a1
0x34b655…2a6f
2 touches
0 conflicts
0x07c94816…b666
0x34b655…2a6f
2 touches
0 conflicts
0x19b4e3fd…3821
0x34b655…2a6f
2 touches
0 conflicts
0x343bff7a…acac
0x34b655…2a6f
2 touches
0 conflicts
0x38bdc5d3…a632
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity