pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,816,718
← previous block
next block →
recent activity
Analyzing
Block #73,816,718
8 transactions · 7 stateful · 2026-05-11 04:34:51 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,816,718
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x98717539
· blocks 1
#5
setData
#6
0x6a015ce3
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a2657f5…e008
0x34b655…2a6f
4 touches
1 conflict
0xb81d3ee7…3947
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x041a094f…a3b7
0x34b655…2a6f
2 touches
0 conflicts
0x23b2399c…6e4b
0x34b655…2a6f
2 touches
0 conflicts
0x375b6201…9c1e
0x34b655…2a6f
2 touches
0 conflicts
0x39c9325f…5a4e
0x34b655…2a6f
2 touches
0 conflicts
0x417b3068…c9a8
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
0x8a2657f5c3…4ce008
Audit this contract →
← previous block
·
next block →
recent activity