pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,213,993
← previous block
next block →
recent activity
Analyzing
Block #72,213,993
8 transactions · 7 stateful · 2026-05-03 18:23:15 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
#72,213,993
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x98717539
#3
permit2TransferAndMulticall
· blocks 1
#4
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
setData
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3006de0…9726
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xc3006de0…9727
0x188d58…ea8e
2 touches
0 conflicts
0xc3006de0…9728
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0xd18a8dca…4530
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:
0x188d586d…f9ea8e
1 conflict on slot
0xc3006de0bc…f59726
Audit this contract →
← previous block
·
next block →
recent activity