pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,971,980
← previous block
next block →
recent activity
Analyzing
Block #73,971,980
9 transactions · 6 stateful · 2026-05-11 21:48:50 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,971,980
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a024f3a
#2
0x1ffa3c9b
#3
0x39435dac
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0xed82b078
#7
0x6a024f3a
#8
setData
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8b40281…952e
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x2ed00f98…da9f
0x34b655…2a6f
4 touches
1 conflict
0x71834f1e…6495
0x34b655…2a6f
4 touches
1 conflict
0x2a5828a2…38c8
0x065c9d…c394
2 touches
0 conflicts
0x5a003a00…a0f0
0x065c9d…c394
2 touches
0 conflicts
0xaf1e30a2…fa08
0x065c9d…c394
2 touches
0 conflicts
0xe355bf38…faf1
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
1 conflict on slot
0xa8b40281f7…17952e
Audit this contract →
← previous block
·
next block →
recent activity