pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,666,703
← previous block
next block →
recent activity
Analyzing
Block #74,666,703
15 transactions · 10 stateful · 2026-05-15 03:02:18 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,666,703
· 15 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#2
updatePrices
#5
execPerpOps
#6
execPerpOps
#7
0x98717539
#8
updateDataFeedsValuesPartial
#9
execFwdPositionOps
#10
execFwdPositionOps
#11
forward
#12
forward
#13
0xed82b078
#14
setData
#3
updatePrices
· blocks 1
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x10814d14…cdda
0x34b655…2a6f
2 touches
0 conflicts
0x430b92ea…6f54
0x34b655…2a6f
2 touches
0 conflicts
0x430b92ea…6f55
0x34b655…2a6f
2 touches
0 conflicts
0x4a830181…d1df
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:
0xab35264b…1cfa38
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity