pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,958,376
← previous block
next block →
recent activity
Analyzing
Block #74,958,376
11 transactions · 7 stateful · 2026-05-16 11:29:45 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,958,376
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
0x98717539
· blocks 1
#4
0x98717539
#5
forward
#6
0xed82b078
#7
updateDataFeedsValuesPartial
#8
0x6a0855a0
#9
setData
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a9478a1…7758
0x34b655…2a6f
4 touches
1 conflict
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0x7b6d2deb…dde0
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x08b925ce…7f5f
0x065c9d…c394
2 touches
0 conflicts
0x1dc67b57…9be3
0x065c9d…c394
2 touches
0 conflicts
0x5a076ec1…e215
0x065c9d…c394
2 touches
0 conflicts
0x836dfae4…35de
0x065c9d…c394
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:
Perpl
1 conflict on slot
0x1a9478a121…c27758
Audit this contract →
← previous block
·
next block →
recent activity