pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,918,560
← previous block
next block →
recent activity
Analyzing
Block #74,918,560
9 transactions · 8 stateful · 2026-05-16 07:03:08 UTC
Parallelism
67
/100
Blocked
38
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,918,560
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
updateDataFeedsValuesPartial
#4
setData
#7
0xed82b078
#8
0x39435dac
#2
0x76368669
· blocks 1
#5
0x0c7abd22
#6
createModule
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x7825cf3b…5acb
0x065c9d…c394
4 touches
1 conflict
0x30276c1c…47b4
0x2a68ba…90c5
4 touches
1 conflict
0x791a7f4c…0b07
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c4
0x1b6862…e19c
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:
USDC (USDC)
1 conflict on slot
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity