pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,289,712
← previous block
next block →
recent activity
Analyzing
Block #74,289,712
8 transactions · 7 stateful · 2026-05-13 09:04:51 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,289,712
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x98717539
#4
0x6a043f2a
#5
setData
#6
swapExactIn
· blocks 1
#7
swapExactIn
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
0x00000000…0004
0xd5b70d…615b
4 touches
1 conflict
0xc3006de0…9728
0x188d58…ea8e
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
4 touches
1 conflict
0x36b49472…3c5b
0x699abc…6a3b
4 touches
1 conflict
0x70f06c02…cc4f
0x699abc…6a3b
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0xd5b70d…615b
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:
0xd5b70d70…f4615b
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity