pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,701,811
← previous block
next block →
recent activity
Analyzing
Block #75,701,811
10 transactions · 10 stateful · 2026-05-19 22:22:45 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,701,811
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#4
updateDataFeedsValuesPartial
#5
setData
#6
updatePriceFeedsIfNecessary
#7
0x5339c59f
#8
0x39435dac
#9
0x39435dac
#2
0x1094dc9f
#3
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe90b7bce…c2e0
0xfa32f9…f3f0
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x9bf064a6…4f04
0x2a68ba…90c5
4 touches
1 conflict
0x99f666e3…b2a2
0x3bd359…433a
4 touches
1 conflict
0xfe3bddd2…8b48
0x3bd359…433a
4 touches
1 conflict
0x4e368b2b…09ac
0x754704…b603
4 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
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:
0xfa32f9ec…fef3f0
1 conflict on slot
0xe90b7bceb6…a7c2e0
Audit this contract →
← previous block
·
next block →
recent activity