pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,566,020
← previous block
next block →
recent activity
Analyzing
Block #74,566,020
11 transactions · 10 stateful · 2026-05-14 15:49:24 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,566,020
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6667b6…6346
#2
0x05ee6a22
· blocks 1
#3
0xed82b078
#4
0x39435dac
#6
updateDataFeedsValuesPartial
#7
0xed82b078
· blocks 1
#9
0x6a05ef7b
#10
setData
#5
exchange
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6aa3628d…2ea3
0x849831…5081
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3c223c30…06e6
0x3bd359…433a
4 touches
1 conflict
0x00000000…0002
0x74d80e…25d4
4 touches
1 conflict
0x00000000…0005
0x74d80e…25d4
4 touches
1 conflict
0x00000000…0014
0x74d80e…25d4
4 touches
1 conflict
0x00000000…001a
0x74d80e…25d4
4 touches
1 conflict
0x00000000…001b
0x74d80e…25d4
4 touches
1 conflict
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:
0x8498312a…f55081
1 conflict on slot
0x6aa3628d88…1c2ea3
Audit this contract →
← previous block
·
next block →
recent activity