pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,977,866
← previous block
next block →
recent activity
Analyzing
Block #73,977,866
11 transactions · 9 stateful · 2026-05-11 22:28:22 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,977,866
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x39ecce49
#2
0x39435dac
· blocks 1
#3
approve
#4
0x0c7abd22
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
setData
#10
0x39435dac
#5
0x0f6795d9
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x139aab…382b
2 touches
0 conflicts
0x00000000…0001
0x139aab…382b
2 touches
0 conflicts
0x00000000…0003
0x139aab…382b
2 touches
0 conflicts
0x1566ca5d…1f77
0x34b655…2a6f
2 touches
0 conflicts
0x28933977…81c5
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
0xf6476f21e7…f83580
Audit this contract →
← previous block
·
next block →
recent activity