pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,596,487
← previous block
next block →
recent activity
Analyzing
Block #95,596,487
10 transactions · 10 stateful · 2026-08-13 09:33:38 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,596,487
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x39435dac
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
· blocks 1
#7
setData
#8
0x59558d29
#9
0x39435dac
#5
0x0f6795d9
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7e3d0073…65e8
0x34b655…2a6f
4 touches
1 conflict
0x0ec74d82…fdd9
0x34b655…2a6f
4 touches
1 conflict
0x4bc1abab…5874
0x34b655…2a6f
2 touches
0 conflicts
0x5f7d122d…f965
0x34b655…2a6f
2 touches
0 conflicts
0x69523dd3…faa2
0x34b655…2a6f
2 touches
0 conflicts
0x73d70be1…c3d1
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
0x31b3992285…921e66
Audit this contract →
← previous block
·
next block →
recent activity