pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,565,558
← previous block
next block →
recent activity
Analyzing
Block #93,565,558
8 transactions · 8 stateful · 2026-08-06 06:47:08 UTC
Parallelism
63
/100
Blocked
25
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,565,558
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0f6795d9
#2
0x0f6795d9
#3
placeAndExecuteMarketSell
· blocks 2
#6
setData
#7
0xc7e3ec2c
#4
placeAndExecuteMarketSell
· blocks 1
#5
placeAndExecuteMarketSell
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x74afcc6c…a4dd
0x851145…3f07
4 touches
1 conflict
0x1bf8d2af…d140
0x34b655…2a6f
2 touches
0 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
2 touches
0 conflicts
0x69a45f39…39aa
0x34b655…2a6f
2 touches
0 conflicts
0x6af385b8…971c
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:
USDC (USDC)
3 conflicts on slot
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity