pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,686,907
← previous block
next block →
recent activity
Analyzing
Block #73,686,907
9 transactions · 8 stateful · 2026-05-10 14:00:12 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,686,907
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x121eab2f
#2
0x6a008fe4
#3
updatePrices
#4
0x39435dac
· blocks 2
#6
updateDataFeedsValuesPartial
#7
setData
#5
0x98717539
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa8a1c54…ead3
0x34b655…2a6f
6 touches
3 conflicts
0x3e733ae4…4598
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0x148f33fb…5af3
0x34b655…2a6f
4 touches
1 conflict
0xe3693869…566b
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x2e4d015b…d927
0x065c9d…c394
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
3 conflicts on slot
0xaa8a1c5424…edead3
Audit this contract →
← previous block
·
next block →
recent activity