pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,506,160
← previous block
next block →
recent activity
Analyzing
Block #93,506,160
9 transactions · 7 stateful · 2026-08-06 01:48:33 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,506,160
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
updateDataFeedsValuesPartial
#3
executeBatch
#4
0x3f5c179b
· blocks 1
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x59558d29
#5
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x67e4f554…12a3
0x851145…3f07
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x27099c8c…d9d5
0x34b655…2a6f
2 touches
0 conflicts
0x2def1f88…9b98
0x34b655…2a6f
2 touches
0 conflicts
0x5930b10a…dcdf
0x34b655…2a6f
2 touches
0 conflicts
0x5930b10a…dce0
0x34b655…2a6f
2 touches
0 conflicts
0x5b4345ae…f9d1
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