pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,140,892
← previous block
next block →
recent activity
Analyzing
Block #75,140,892
9 transactions · 9 stateful · 2026-05-17 07:48:35 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,140,892
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x6a09734b
#6
setData
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed08606b…abd5
0x34b655…2a6f
4 touches
1 conflict
0x41d3bfa5…523e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00f7e3b7…e015
0x188d58…ea8e
2 touches
0 conflicts
0x00f7e3b7…e016
0x188d58…ea8e
2 touches
0 conflicts
0xa4e3b3b1…0911
0x2a68ba…90c5
2 touches
0 conflicts
0x1e5033bb…4c23
0x3bd359…433a
2 touches
0 conflicts
0xa980598e…ec52
0x3bd359…433a
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
0xed08606b4a…78abd5
Audit this contract →
← previous block
·
next block →
recent activity