pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,389,267
← previous block
next block →
recent activity
Analyzing
Block #74,389,267
11 transactions · 9 stateful · 2026-05-13 20:07:12 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,389,267
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
0x5bf9264c
#3
0x5bf9264c
#4
0x98717539
#5
0x6df9e92b
#6
updateDataFeedsValuesPartial
#7
0x6a04da68
#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
0x742436a7…c4d4
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xffe431af…8faa
0x065c9d…c394
2 touches
0 conflicts
0xfb083229…0138
0x2a68ba…90c5
2 touches
0 conflicts
0x8fa7a69c…8fd7
0x34405e…7777
2 touches
0 conflicts
0xa9ef8045…f71e
0x34405e…7777
2 touches
0 conflicts
0x10814d14…cdda
0x34b655…2a6f
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
0x742436a7e5…69c4d4
Audit this contract →
← previous block
·
next block →
recent activity