pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,594,914
← previous block
next block →
recent activity
Analyzing
Block #74,594,914
11 transactions · 10 stateful · 2026-05-14 19:02:49 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,594,914
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6df9e92b
· blocks 1
#2
0xa96df62f
#3
updatePrices
#5
forward
#6
updateDataFeedsValuesPartial
#7
0x5339c59f
#8
0xed82b078
#9
setData
#10
0x39435dac
#4
0x52f07cf9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xa7283d…0ace
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x536e2740…61ac
0x3bd359…433a
4 touches
1 conflict
0x8fa7a69c…8fd7
0x17a62e…7777
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x00000000…000b
0x5075ea…d70f
2 touches
0 conflicts
0xcba59bf3…8d1d
0xa7283d…0ace
2 touches
0 conflicts
0xcba59bf3…8d1e
0xa7283d…0ace
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:
0xa7283d07…f90ace
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity