pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,248,584
← previous block
next block →
recent activity
Analyzing
Block #74,248,584
11 transactions · 11 stateful · 2026-05-13 04:31:27 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,248,584
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x575c0012
#2
0x6a03ff17
#3
supply
#4
updateDataFeedsValuesPartial
#5
updatePriceFeedsIfNecessary
#6
forward
#7
0x39435dac
#8
setData
#9
0x39435dac
· blocks 1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41d3bfa5…523e
0x34b655…2a6f
4 touches
1 conflict
0x768cffcd…2648
0x34b655…2a6f
4 touches
1 conflict
0xb8228d38…3953
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0036
0x39f901…6bdf
2 touches
0 conflicts
0xf303862a…a3b1
0x39f901…6bdf
2 touches
0 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
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:
0x34b6552d…112a6f
1 conflict on slot
0x41d3bfa533…31523e
Audit this contract →
← previous block
·
next block →
recent activity