pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,811,060
← previous block
next block →
recent activity
Analyzing
Block #91,811,060
10 transactions · 7 stateful · 2026-07-31 03:40:25 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,811,060
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#4
0x3f5c179b
#5
0x3f5c179b
#7
0x57368ddf
#8
execOrders
#9
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a3d2527…8ca0
0x34b655…2a6f
4 touches
1 conflict
0x530e9903…f9f9
0x34b655…2a6f
4 touches
1 conflict
0x772ab420…c2f6
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0xfecb18c0…01ed
0x34b655…2a6f
4 touches
1 conflict
0x211c747b…db9b
0x34b655…2a6f
2 touches
0 conflicts
0x32d6b06f…436b
0x34b655…2a6f
2 touches
0 conflicts
0x42b10c57…3ee7
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
0x1a3d2527fb…8a8ca0
Audit this contract →
← previous block
·
next block →
recent activity