pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,971,258
← previous block
next block →
recent activity
Analyzing
Block #73,971,258
9 transactions · 7 stateful · 2026-05-11 21:44:02 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,971,258
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
#2
execute
#3
0x39435dac
· blocks 1
#5
0x0c7abd22
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6040987…df02
0x34b655…2a6f
4 touches
1 conflict
0x163c8eca…7b49
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x39ed3b88…cfc0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0001
0x139aab…382b
2 touches
0 conflicts
0x00000000…0003
0x139aab…382b
2 touches
0 conflicts
0x1cfcf01a…26ac
0x34b655…2a6f
2 touches
0 conflicts
0x2aab0897…78f7
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
0xe6040987fc…efdf02
Audit this contract →
← previous block
·
next block →
recent activity