pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,294,133
← previous block
next block →
recent activity
Analyzing
Block #94,294,133
10 transactions · 9 stateful · 2026-08-08 19:58:08 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,294,133
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
#2
updateDataFeedsValuesPartial
#3
executeBatch
#4
placeAndExecuteMarketSell
· blocks 1
#6
0x6a778ac8
#7
setData
#8
0x39435dac
#9
0xc7e3ec2c
#5
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a9e9bd1…5368
0x2a68ba…90c5
4 touches
1 conflict
0xee4f1ffb…8e9a
0xa6afd3…d132
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0a5b3368…6d07
0x34b655…2a6f
2 touches
0 conflicts
0x0fe1e6e0…f553
0x34b655…2a6f
2 touches
0 conflicts
0x2a34bb88…04d5
0x34b655…2a6f
2 touches
0 conflicts
0x2a34bb88…04d6
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e66
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
0x2a9e9bd1e2…355368
Audit this contract →
← previous block
·
next block →
recent activity