pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,003,639
← previous block
next block →
recent activity
Analyzing
Block #75,003,639
8 transactions · 6 stateful · 2026-05-16 16:32:59 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,003,639
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xbb5d006a
· blocks 2
#4
0xed82b078
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x39435dac
#2
0xbb5d006a
· blocks 1
#3
0xbb5d006a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38370fa5…04ae
0x541997…f5a0
6 touches
3 conflicts
0x38370fa5…04af
0x541997…f5a0
6 touches
3 conflicts
0x02f33632…bfd0
0x541997…f5a0
5 touches
3 conflicts
0x3e49348b…9445
0x34b655…2a6f
2 touches
0 conflicts
0x6efd1872…7582
0x34b655…2a6f
2 touches
0 conflicts
0xba9f88e8…9c33
0x34b655…2a6f
2 touches
0 conflicts
0xd30a4208…3cd2
0x34b655…2a6f
2 touches
0 conflicts
0xd98b3c10…67b8
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:
0x541997e9…30f5a0
3 conflicts on slot
0x38370fa51d…5104ae
Audit this contract →
← previous block
·
next block →
recent activity