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