pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,600,606
← previous block
next block →
recent activity
Analyzing
Block #74,600,606
10 transactions · 8 stateful · 2026-05-14 19:41:07 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,600,606
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a0625cb
#2
updatePrices
#3
0x98717539
· blocks 1
#5
0x6df9e92b
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x633c55…7509
#9
multicall
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06c10d86…6883
0x34b655…2a6f
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x9a291a56…9a9c
0x34b655…2a6f
4 touches
1 conflict
0xa92c8763…6d7f
0x34b655…2a6f
4 touches
1 conflict
0xbad68552…e6bf
0x34b655…2a6f
4 touches
1 conflict
0xf3808e5a…dbfb
0x34b655…2a6f
4 touches
1 conflict
0x3e1f7818…2fc8
0x34b655…2a6f
4 touches
1 conflict
0x5e9a6588…01d2
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x06c10d86e2…d56883
Audit this contract →
← previous block
·
next block →
recent activity