pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,073,508
← previous block
next block →
recent activity
Analyzing
Block #95,073,508
7 transactions · 7 stateful · 2026-08-11 13:29:32 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.29
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,073,508
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#2
0x0f6795d9
· blocks 1
#3
0x3f5c179b
#5
setData
#6
0x59558d29
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf039e2f8…3d8a
0x34b655…2a6f
4 touches
1 conflict
0x5cacfb02…ef32
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x243daf52…fd2b
0x34b655…2a6f
2 touches
0 conflicts
0x2c145401…09fd
0x34b655…2a6f
2 touches
0 conflicts
0x35c29640…8779
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
0xf039e2f8da…b73d8a
Audit this contract →
← previous block
·
next block →
recent activity