pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,555,705
← previous block
next block →
recent activity
Analyzing
Block #93,555,705
8 transactions · 4 stateful · 2026-08-06 05:57:36 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,555,705
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#3
placeAndExecuteMarketBuy
#4
placeAndExecuteMarketSell
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#2
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb0b1d43…9559
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x3d0a1339…f545
0x34b655…2a6f
2 touches
0 conflicts
0x43e15ca4…039d
0x34b655…2a6f
2 touches
0 conflicts
0x742436a7…c4d4
0x34b655…2a6f
2 touches
0 conflicts
0x803eb45d…00bd
0x34b655…2a6f
2 touches
0 conflicts
0xba228f10…2593
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
0xeb0b1d4366…fc9559
Audit this contract →
← previous block
·
next block →
recent activity