pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,592,754
← previous block
next block →
recent activity
Analyzing
Block #93,592,754
12 transactions · 12 stateful · 2026-08-06 09:03:51 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,592,754
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6ad2e98b
· blocks 2
#2
0xab083028
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#7
allocate
#9
transfer
#10
setData
#11
signIn
#6
placeAndExecuteMarketSell
· blocks 1
#8
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07b86c51…cdae
0x2a68ba…90c5
6 touches
3 conflicts
0x047d44f6…df4c
0x851145…3f07
5 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x02ea2ac5…913f
0x851145…3f07
4 touches
1 conflict
0x19e49883…3293
0x851145…3f07
4 touches
1 conflict
0xcfeed415…e4ab
0x851145…3f07
4 touches
1 conflict
0x39977254…07b1
0x2b46c0…1669
2 touches
0 conflicts
0x3a3e7727…36c5
0x2b46c0…1669
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