pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,259,820
← previous block
next block →
recent activity
Analyzing
Block #74,259,820
11 transactions · 10 stateful · 2026-05-13 05:46:03 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,259,820
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
#2
0x6a041092
#3
0x6a041092
#4
0x39435dac
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x5339c59f
#8
0x5339c59f
#9
0xe9316489
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9d2cf20…a668
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x019883…2a9a
2 touches
0 conflicts
0x00000000…0002
0x019883…2a9a
2 touches
0 conflicts
0x00000000…0003
0x019883…2a9a
2 touches
0 conflicts
0x00000000…0015
0x019883…2a9a
2 touches
0 conflicts
0x6538b8da…0f0b
0x0cc9b2…7777
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
0xb9d2cf2005…28a668
Audit this contract →
← previous block
·
next block →
recent activity