pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,757,747
← previous block
next block →
recent activity
Analyzing
Block #75,757,747
10 transactions · 8 stateful · 2026-05-20 04:35:08 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,757,747
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a0d3a74
#2
approve
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0xe7be4706
· blocks 1
#7
0xed82b078
#8
0x6a0d3a74
#9
setData
#3
swap
#6
0xe7be4706
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6455d1f…1029
0x754704…b603
4 touches
1 conflict
0x0d0b2509…074d
0x3bd359…433a
4 touches
1 conflict
0x8719f49b…d51d
0x350035…7777
2 touches
1 conflict
0x67d47cb1…3fa0
0x188d58…ea8e
2 touches
0 conflicts
0x67d47cb1…3fa2
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba61
0x188d58…ea8e
2 touches
0 conflicts
0xbc467e7a…af36
0x21e325…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:
USDC (USDC)
1 conflict on slot
0xe6455d1fbe…eb1029
Audit this contract →
← previous block
·
next block →
recent activity