pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,208,213
← previous block
next block →
recent activity
Analyzing
Block #96,208,213
9 transactions · 7 stateful · 2026-08-15 12:52:02 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,208,213
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5acec890
#3
0xcffefd2e
· blocks 1
#4
updateDataFeedsValuesPartial
#5
executeBatch
#6
0xcffefd2e
#8
setData
#7
0xcffefd2e
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd6c6dcfb…677c
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x376c9634…97d2
0x34b655…2a6f
4 touches
1 conflict
0x0ad94e1a…dc55
0x34b655…2a6f
2 touches
0 conflicts
0x18cf36a6…a3a3
0x34b655…2a6f
2 touches
0 conflicts
0x28122190…2c8e
0x34b655…2a6f
2 touches
0 conflicts
0x2a49f3bf…713b
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
1 conflict on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity