pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,325,814
← previous block
next block →
recent activity
Analyzing
Block #74,325,814
11 transactions · 10 stateful · 2026-05-13 13:05:06 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,325,814
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0x1ffa3c9b
#3
0x76368669
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
0x1a945f9c
· blocks 1
#8
closeTrade
#9
0x6a047779
#10
setData
#7
0xd10227eb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x158fc8d2…9bb3
0x065c9d…c394
2 touches
0 conflicts
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x60b24061…7c23
0x188d58…ea8e
2 touches
0 conflicts
0x60b24061…7c25
0x188d58…ea8e
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:
LeverUp: LeverUp
1 conflict on slot
0xa8abcc1955…203d83
Audit this contract →
← previous block
·
next block →
recent activity