pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,148,608
← previous block
next block →
recent activity
Analyzing
Block #76,148,608
9 transactions · 7 stateful · 2026-05-22 00:00:10 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,148,608
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#3
0x9e76c652
#5
executeBatch
· blocks 1
#7
0x0f6795d9
#8
setData
#4
0x0f6795d9
#6
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x00000000…0006
0x2ab50b…5c41
2 touches
0 conflicts
0x00e09525…a2f4
0x2ab50b…5c41
2 touches
0 conflicts
0x017130f6…f21c
0x2ab50b…5c41
2 touches
0 conflicts
0x0c24d17f…1e99
0x2ab50b…5c41
2 touches
0 conflicts
0x12f2de54…9748
0x2ab50b…5c41
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity