pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,308,997
← previous block
next block →
recent activity
Analyzing
Block #74,308,997
8 transactions · 7 stateful · 2026-05-13 11:13:12 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,308,997
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xccf50a51
· blocks 1
#3
0x98717539
#4
0x98717539
#5
updatePriceFeedsIfNecessary
#6
updateDataFeedsValuesPartial
#7
setData
#2
0xccf50a51
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
0x6677f92f…b7cd
0x0555e3…2b9c
4 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x9e223b01…38b2
0x3bd359…433a
4 touches
1 conflict
0x0db076db…5325
0x065c9d…c394
4 touches
1 conflict
0x3ebea2a4…9673
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0x094452…0a09
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:
0x0555e30d…0d2b9c
1 conflict on slot
0x6677f92fde…85b7cd
Audit this contract →
← previous block
·
next block →
recent activity
Feature requests
→