pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,094,032
← previous block
next block →
recent activity
Analyzing
Block #75,094,032
18 transactions · 15 stateful · 2026-05-17 02:35:57 UTC
Parallelism
78
/100
Blocked
53
%
Avg conflicts / tx
0.78
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,094,032
· 18 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 4
#5
0x6a092a05
#6
0x6a092a05
#7
0x98717539
· blocks 4
#11
updateDataFeedsValuesPartial
#12
0x6a092a05
#13
exactInputSingle
#15
setData
#16
0xd53e7c84
#2
0x0c7abd22
· blocks 2
#8
0x98717539
· blocks 2
#14
0x5339c59f
#17
0x39435dac
#3
0x0c7abd22
· blocks 1
#9
0x98717539
· blocks 1
#4
0x0c7abd22
#10
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
7
w0
8
w1
9
w2
10
w3
14
w1
17
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x17ca7036…1e14
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 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:
0x1b68626d…2de19c
6 conflicts on slot
0x0000000000…000012
Audit this contract →
← previous block
·
next block →
recent activity