pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,512,432
← previous block
next block →
recent activity
Analyzing
Block #93,512,432
8 transactions · 8 stateful · 2026-08-06 02:20:05 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,512,432
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0xb2d4797b
#3
placeAndExecuteMarketSell
· blocks 2
#6
0x0f6795d9
#7
setData
#4
placeAndExecuteMarketSell
· blocks 1
#5
batchUpdate
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
0x07b86c51…cdae
0x2a68ba…90c5
6 touches
3 conflicts
0x57fca75e…fa5d
0x851145…3f07
5 touches
3 conflicts
0x513bcef5…048e
0x01bff4…1071
4 touches
1 conflict
0x3d9eb674…b3fb
0x754704…b603
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x0edf889a…ce9d
0x01bff4…1071
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xcd621226…2df8
0x368ee5…7ca4
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
3 conflicts on slot
0x07b86c515d…73cdae
Audit this contract →
← previous block
·
next block →
recent activity