pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,338,301
← previous block
next block →
recent activity
Analyzing
Block #73,338,301
12 transactions · 10 stateful · 2026-05-08 23:15:25 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,338,301
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x39435dac
#3
0x5bf9264c
#4
0x5bf9264c
#6
updateDataFeedsValuesPartial
#7
0x69fe6f04
#8
0xeffdedb0
#9
setData
#10
0x044e6100
#11
0x39435dac
#5
createModule
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12137d45…f20b
0x065c9d…c394
2 touches
0 conflicts
0x0ef74796…cd18
0x0a3323…0a3c
2 touches
0 conflicts
0x366be501…7a02
0x0a3323…0a3c
2 touches
0 conflicts
0xff393f19…4dd2
0x0a3323…0a3c
2 touches
0 conflicts
0x00000000…0000
0x0d73bf…be07
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:
0x188d586d…f9ea8e
1 conflict on slot
0x01e7b86585…4d6e6f
Audit this contract →
← previous block
·
next block →
recent activity