pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,682,497
← previous block
next block →
recent activity
Analyzing
Block #93,682,497
10 transactions · 8 stateful · 2026-08-06 16:35:00 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,682,497
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
placeAndExecuteMarketBuy
#5
0x0f6795d9
· blocks 2
#8
setData
#9
0x39435dac
#6
0x0f6795d9
· blocks 1
#7
0x0f6795d9
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
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc6b9bb4b…145a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5ddf85a7…78c8
0x34b655…2a6f
4 touches
1 conflict
0xdaf4f143…58d4
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…003d
0x447d2e…e9f5
2 touches
0 conflicts
0x2506f9b1…6e68
0x447d2e…e9f5
2 touches
0 conflicts
0x2e221981…a4c6
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:
Perpl
3 conflicts on slot
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity