pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,114,101
← previous block
next block →
recent activity
Analyzing
Block #76,114,101
11 transactions · 9 stateful · 2026-05-21 20:10:20 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,114,101
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
batchUpdate
#5
updatePrices
· blocks 1
#7
updateDataFeedsValuesPartial
#8
setData
#9
execFwdPositionOps
#10
execFwdPositionOps
#6
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x063f4abe…1564
0x065c9d…c394
2 touches
0 conflicts
0x4698c00f…01a6
0x065c9d…c394
2 touches
0 conflicts
0x749f76ef…1a8c
0x065c9d…c394
2 touches
0 conflicts
0xe8ba1b8e…9d8f
0x065c9d…c394
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:
0xab35264b…1cfa38
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity