pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,986,974
← previous block
next block →
recent activity
Analyzing
Block #75,986,974
8 transactions · 7 stateful · 2026-05-21 06:03:11 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,986,974
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#4
0xd10227eb
#6
batchUpdate
#7
setData
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e653769…cb11
0x34b655…2a6f
4 touches
1 conflict
0xf9b8ae99…32b3
0x34b655…2a6f
4 touches
1 conflict
0x138aa8a0…71d6
0x34b655…2a6f
2 touches
0 conflicts
0x36e87008…0bf4
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x48e4e1cf…f91b
0x34b655…2a6f
2 touches
0 conflicts
0x699e5877…05ab
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
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
0x8e6537696a…67cb11
Audit this contract →
← previous block
·
next block →
recent activity