pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,390,234
← previous block
next block →
recent activity
Analyzing
Block #73,390,234
12 transactions · 10 stateful · 2026-05-09 05:00:51 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,390,234
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xbbb036a8
#2
0x76368669
#3
0xe7be4706
· blocks 1
#4
0xe7be4706
#5
0x98717539
#7
updateDataFeedsValuesPartial
#8
withdraw
#9
0xeffdedb0
#10
setData
#11
0x39435dac
#6
0xe7be4706
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d0b2509…074d
0x3bd359…433a
4 touches
1 conflict
0xe6455d1f…1029
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x60b24061…7c23
0x188d58…ea8e
2 touches
0 conflicts
0x60b24061…7c24
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba61
0x188d58…ea8e
2 touches
0 conflicts
0x05a30e31…2713
0x3bd359…433a
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:
0x3bd359c1…15433a
1 conflict on slot
0x0d0b2509ae…4b074d
Audit this contract →
← previous block
·
next block →
recent activity