pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,527,002
← previous block
next block →
recent activity
Analyzing
Block #76,527,002
7 transactions · 5 stateful · 2026-05-23 17:59:41 UTC
Parallelism
71
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,527,002
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x98717539
· blocks 1
#4
0x0f6795d9
#5
0x0f6795d9
#6
setData
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5b39cea…2f9b
0x34b655…2a6f
4 touches
1 conflict
0x49b0842d…0a93
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xcab2b82c…47bc
0x34b655…2a6f
4 touches
1 conflict
0x0f6aa0f2…dc95
0x34b655…2a6f
2 touches
0 conflicts
0x286cc12c…79f7
0x34b655…2a6f
2 touches
0 conflicts
0x2c7796c7…0d29
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
0xd5b39cea7c…462f9b
Audit this contract →
← previous block
·
next block →
recent activity