pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,924,365
← previous block
next block →
recent activity
Analyzing
Block #93,924,365
11 transactions · 10 stateful · 2026-08-07 12:51:25 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,924,365
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x3f5c179b
#3
0x0c7abd22
#4
execFwdPositionOps
#5
0x6df9e92b
· blocks 2
#8
updateDataFeedsValuesPartial
#9
setData
#10
execOrders
#6
0x6df9e92b
· blocks 1
#7
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x116e7d…d8f1
6 touches
3 conflicts
0x00000000…0002
0x116e7d…d8f1
6 touches
3 conflicts
0x44ad89ba…cf83
0x350035…7777
6 touches
3 conflicts
0x692a4122…76b8
0x350035…7777
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0xb7143610…adc4
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0003
0x116e7d…d8f1
6 touches
3 conflicts
0x2506f9b1…6e68
0x447d2e…e9f5
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:
0x116e7d07…d7d8f1
3 conflicts on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity