pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,506,077
← previous block
next block →
recent activity
Analyzing
Block #76,506,077
12 transactions · 10 stateful · 2026-05-23 15:40:25 UTC
Parallelism
75
/100
Blocked
30
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,506,077
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
#2
execute
#3
0x5bf9264c
#4
0x5bf9264c
#5
0xed82b078
· blocks 2
#9
updateDataFeedsValuesPartial
#10
setData
#11
0x39435dac
#6
0xed82b078
#7
0xed82b078
· blocks 1
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x9c11d943…f33a
0x0555e3…2b9c
2 touches
0 conflicts
0x95523e2a…4c01
0x065c9d…c394
2 touches
0 conflicts
0xa5074c91…a06b
0x065c9d…c394
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
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:
0xa6afd386…b0d132
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity