pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,855,441
← previous block
next block →
recent activity
Analyzing
Block #93,855,441
10 transactions · 8 stateful · 2026-08-07 07:04:27 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,855,441
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcbbdb31a
#2
forward
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
· blocks 1
#6
updatePosition
#8
setData
#9
0xc7e3ec2c
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfecb18c0…01ed
0x34b655…2a6f
4 touches
1 conflict
0xfd42a6b9…4c81
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0226b774…a9ed
0x34b655…2a6f
2 touches
0 conflicts
0x032b8c7a…bbc1
0x34b655…2a6f
2 touches
0 conflicts
0x0463db49…5d05
0x34b655…2a6f
2 touches
0 conflicts
0x089aecdd…92ac
0x34b655…2a6f
2 touches
0 conflicts
0x112c35bc…2afc
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
0xfecb18c068…6e01ed
Audit this contract →
← previous block
·
next block →
recent activity