pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,490,975
← previous block
next block →
recent activity
Analyzing
Block #94,490,975
9 transactions · 8 stateful · 2026-08-09 12:37:12 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,490,975
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x0f6795d9
· blocks 1
#3
placeAndExecuteMarketSell
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#4
batchUpdate
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x312529c0…cd3c
0x34b655…2a6f
4 touches
1 conflict
0x70eec2ed…f791
0x34b655…2a6f
4 touches
1 conflict
0xdc57bfe3…ae86
0x065c9d…c394
3 touches
1 conflict
0x14002e42…475a
0x34b655…2a6f
2 touches
0 conflicts
0x38855b14…b4ec
0x34b655…2a6f
2 touches
0 conflicts
0x3cf50d44…961b
0x34b655…2a6f
2 touches
0 conflicts
0x4e58f1d6…2fca
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x0778475bb2…63bd75
Audit this contract →
← previous block
·
next block →
recent activity