pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,501,894
← previous block
next block →
recent activity
Analyzing
Block #74,501,894
7 transactions · 5 stateful · 2026-05-14 08:36:55 UTC
Parallelism
71
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,501,894
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swapExactIn
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x39435dac
· blocks 1
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe181f491…f4e3
0x34b655…2a6f
4 touches
1 conflict
0xa3ff1ab2…8ae3
0x34b655…2a6f
4 touches
1 conflict
0x543da691…8f99
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdef19d99…c0a9
0x34b655…2a6f
4 touches
1 conflict
0xb2471674…39bd
0x34b655…2a6f
2 touches
0 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
2 touches
0 conflicts
0xea02471d…1542
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xe181f491d8…b1f4e3
Audit this contract →
← previous block
·
next block →
recent activity