pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,103,172
← previous block
next block →
recent activity
Analyzing
Block #75,103,172
18 transactions · 17 stateful · 2026-05-17 03:36:53 UTC
Parallelism
83
/100
Blocked
41
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,103,172
· 18 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
execute_route
· blocks 1
#4
0x67098489
· blocks 2
#7
0x6a09384c
#8
exactOutputSingle
#10
0x98717539
· blocks 2
#11
updateDataFeedsValuesPartial
#12
0x5339c59f
#14
0x6a09384c
#15
setData
#2
0x0c7abd22
#5
execute
· blocks 1
#9
exactOutputSingle
#13
0x5339c59f
#16
0x39435dac
· blocks 1
#6
execute
#17
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w0
5
w1
6
w2
9
w1
10
w0
13
w1
16
w1
17
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0x4aa4f53b…899f
0x188d58…ea8e
4 touches
1 conflict
0x4aa4f53b…89a1
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
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