pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,593,568
← previous block
next block →
recent activity
Analyzing
Block #95,593,568
8 transactions · 6 stateful · 2026-08-13 09:18:57 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,593,568
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
aggregate3
#3
0x0f6795d9
· blocks 2
#6
updateDataFeedsValuesPartial
#7
setData
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
4 touches
1 conflict
0xbd20b4e3…e8d3
0x34b655…2a6f
4 touches
1 conflict
0x2f1de8d9…dbad
0x34b655…2a6f
2 touches
0 conflicts
0x3a823597…b343
0x34b655…2a6f
2 touches
0 conflicts
0x41f8f5dd…90f5
0x34b655…2a6f
2 touches
0 conflicts
0x4a90f6e1…695a
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity