pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,990,467
← previous block
next block →
recent activity
Analyzing
Block #75,990,467
11 transactions · 7 stateful · 2026-05-21 06:26:21 UTC
Parallelism
73
/100
Blocked
43
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,990,467
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x98717539
· blocks 3
#3
0x0c7abd22
#4
updateDataFeedsValuesPartial
#5
0x1bb620…1def
#6
0xecb0db…32bc
#7
setData
#9
execOrders
#2
0x98717539
#8
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08d31c28…d50f
0x34b655…2a6f
6 touches
3 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
6 touches
3 conflicts
0x8d0e98f3…7ba0
0x34b655…2a6f
4 touches
1 conflict
0xb138d087…4689
0x34b655…2a6f
4 touches
1 conflict
0x84fb2a36…db89
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
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
0x08d31c2849…fed50f
Audit this contract →
← previous block
·
next block →
recent activity