pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,764,850
← previous block
next block →
recent activity
Analyzing
Block #75,764,850
11 transactions · 7 stateful · 2026-05-20 05:22:28 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,764,850
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
· blocks 1
#2
forward
#3
updateDataFeedsValuesPartial
#4
0x6a0d458c
#5
0xb74d6b…2f68
#6
0xeef674…7783
#7
setData
#8
0x39435dac
· blocks 1
#10
jMMeC
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe54a1f6f…18f2
0x34b655…2a6f
4 touches
1 conflict
0x3ac9e0f2…b632
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x0711ec2d…d973
0x34b655…2a6f
2 touches
0 conflicts
0x2cd10ba5…f946
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x6c042c61…f883
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
0xe54a1f6fdd…7918f2
Audit this contract →
← previous block
·
next block →
recent activity