pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,104,557
← previous block
next block →
recent activity
Analyzing
Block #75,104,557
7 transactions · 5 stateful · 2026-05-17 03:46:07 UTC
Parallelism
57
/100
Blocked
40
%
Avg conflicts / tx
0.43
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,104,557
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
· blocks 2
#2
updateDataFeedsValuesPartial
#3
0x62be7533
#6
setData
#4
0xc2d867a5
· blocks 1
#5
0xc2d867a5
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x33018431…8f5c
0x188d58…ea8e
6 touches
3 conflicts
0x12309510…0ac2
0x000000…012a
6 touches
3 conflicts
0xb0f4dbcb…926a
0x754704…b603
4 touches
1 conflict
0xe069120c…952c
0x000000…012a
4 touches
1 conflict
0x33018431…8f5e
0x188d58…ea8e
4 touches
1 conflict
0x33018431…8f5f
0x188d58…ea8e
4 touches
1 conflict
0x3b99eb5d…2c09
0x188d58…ea8e
4 touches
1 conflict
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:
0x754704bc…afb603
3 conflicts on slot
0x17606ba612…ea1b6e
Audit this contract →
← previous block
·
next block →
recent activity