pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,756,711
← previous block
next block →
recent activity
Analyzing
Block #75,756,711
11 transactions · 7 stateful · 2026-05-20 04:28:14 UTC
Parallelism
73
/100
Blocked
29
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,756,711
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
updateDataFeedsValuesPartial
#4
0x39435dac
#5
0x5339c59f
#6
setData
#7
0x39435dac
#8
0x39435dac
· blocks 1
#9
0x39435dac
· blocks 1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xeebd31ac…0794
0x34b655…2a6f
4 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0xbfca3cd0…5023
0x34b655…2a6f
4 touches
1 conflict
0x9b8800c1…ed12
0x34b655…2a6f
2 touches
0 conflicts
0xac2a0273…7212
0x34b655…2a6f
2 touches
0 conflicts
0xac2a0273…721b
0x34b655…2a6f
2 touches
0 conflicts
0xc03a03cd…fbcf
0x34b655…2a6f
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity