pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,201,009
← previous block
next block →
recent activity
Analyzing
Block #75,201,009
12 transactions · 10 stateful · 2026-05-17 14:30:06 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.42
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,201,009
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
deposit
#2
0x98717539
· blocks 2
#3
0x9e76c652
#4
execOrders
· blocks 2
#5
updateDataFeedsValuesPartial
#6
executeNext
#7
deposit
#8
setData
#11
execOrders
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e49348b…9445
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x7ca7baa7…d46d
0x34b655…2a6f
4 touches
1 conflict
0x8fbde2b3…9b8f
0x34b655…2a6f
4 touches
1 conflict
0x039fd5ab…0d4f
0x2ab50b…5c41
2 touches
0 conflicts
0x05b8ccbb…46bc
0x2ab50b…5c41
2 touches
0 conflicts
0x005fb969…2d97
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
0x3e49348b38…839445
Audit this contract →
← previous block
·
next block →
recent activity