pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,949,196
← previous block
next block →
recent activity
Analyzing
Block #73,949,196
5 transactions · 4 stateful · 2026-05-11 19:17:11 UTC
Parallelism
60
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,949,196
· 5 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#3
updateDataFeedsValuesPartial
#4
setData
#2
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ee110ef…8394
0x34b655…2a6f
4 touches
1 conflict
0x276f568b…69f6
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x018b5be4…ed8c
0x34b655…2a6f
2 touches
0 conflicts
0x04183f8d…069e
0x34b655…2a6f
2 touches
0 conflicts
0x0937595f…16bf
0x34b655…2a6f
2 touches
0 conflicts
0x0c5933fb…b350
0x34b655…2a6f
2 touches
0 conflicts
0x10f5f4d8…572e
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
0x7ee110efcf…e68394
Audit this contract →
← previous block
·
next block →
recent activity