pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,271,017
← previous block
next block →
recent activity
Analyzing
Block #75,271,017
8 transactions · 8 stateful · 2026-05-17 22:18:05 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,271,017
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePosition
#2
0x9e76c652
#3
updateDataFeedsValuesPartial
#4
0x6a0a3f14
#5
setData
#6
execOrders
· blocks 1
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0x04bc535d…281f
0x6657d1…8ccc
2 touches
0 conflicts
0x1c486470…2ff4
0x6657d1…8ccc
2 touches
0 conflicts
0x2a52178e…cdd0
0x6657d1…8ccc
2 touches
0 conflicts
0x36965a8d…c330
0x6657d1…8ccc
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
0x310a7246ab…012dcb
Audit this contract →
← previous block
·
next block →
recent activity