pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,263,737
← previous block
next block →
recent activity
Analyzing
Block #74,263,737
10 transactions · 8 stateful · 2026-05-13 06:12:06 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,263,737
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x98717539
· blocks 2
#4
0x785f5745
#5
0x6a0416ad
#6
setData
#7
0xf79977…58ba
#8
execute
#3
0x98717539
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x578e7f66…1b56
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0df90aad…3d18
0x34b655…2a6f
2 touches
0 conflicts
0x0e1be8a9…b350
0x34b655…2a6f
2 touches
0 conflicts
0x10814d14…cdda
0x34b655…2a6f
2 touches
0 conflicts
0x15f31422…c39a
0x34b655…2a6f
2 touches
0 conflicts
0x2f387761…308c
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:
0x34b6552d…112a6f
1 conflict on slot
0x578e7f6639…de1b56
Audit this contract →
← previous block
·
next block →
recent activity