pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,866,568
← previous block
next block →
recent activity
Analyzing
Block #75,866,568
15 transactions · 13 stateful · 2026-05-20 16:41:35 UTC
Parallelism
87
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,866,568
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a0de4b7
· blocks 1
#3
0x1be2fb9c
#4
updateDataFeedsValuesPartial
#5
updatePosition
#6
0xd53e7c84
#7
forward
#8
batchUpdate
#9
batchUpdate
#10
setData
#11
execOrders
#12
execOrders
#13
execOrders
#14
execOrders
#2
0x6a0de4b7
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
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
0x17507467…a311
0x6657d1…8ccc
2 touches
0 conflicts
0x17aca58f…810a
0x6657d1…8ccc
2 touches
0 conflicts
0x1b2db411…4c9c
0x6657d1…8ccc
2 touches
0 conflicts
0x20274fb7…c3d6
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity