pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,901,758
← previous block
next block →
recent activity
Analyzing
Block #75,901,758
8 transactions · 6 stateful · 2026-05-20 20:35:48 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,901,758
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xaa0506cd
#2
0xbb5d006a
· blocks 1
#4
0x5bf9264c
#5
0x5bf9264c
#6
updateDataFeedsValuesPartial
#7
setData
#3
0xbb5d006a
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
0xf9b0a3e8…95f1
0x541997…f5a0
4 touches
1 conflict
0xf9b0a3e8…95f2
0x541997…f5a0
4 touches
1 conflict
0x499380d8…bced
0x541997…f5a0
4 touches
1 conflict
0xc824469a…641c
0x34b655…2a6f
2 touches
0 conflicts
0x536e2740…61ac
0x3bd359…433a
2 touches
0 conflicts
0xa472d565…9fe4
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0002
0xa7283d…0ace
2 touches
0 conflicts
0xb22f2a1d…d74f
0xa7283d…0ace
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
1 conflict on slot
0xf9b0a3e810…8d95f1
Audit this contract →
← previous block
·
next block →
recent activity