pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,809,387
← previous block
next block →
recent activity
Analyzing
Block #94,809,387
11 transactions · 11 stateful · 2026-08-10 15:20:13 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,809,387
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x39435dac
· blocks 2
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x3f5c179b
#7
executeBatch
#8
0x94defb17
#9
0x6a79eca4
#10
setData
#2
0x4d8dc985
· blocks 1
#3
0x4d8dc985
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3a621f8…75a2
0x34b655…2a6f
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00e21a9f…3583
0x34b655…2a6f
2 touches
0 conflicts
0x2e401ddd…ef19
0x34b655…2a6f
2 touches
0 conflicts
0x30fce83f…a1d6
0x34b655…2a6f
2 touches
0 conflicts
0x3944526b…c457
0x34b655…2a6f
2 touches
0 conflicts
0x42522e76…2592
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:
Perpl
3 conflicts on slot
0xa3a621f8f3…6975a2
Audit this contract →
← previous block
·
next block →
recent activity