pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,923,773
← previous block
next block →
recent activity
Analyzing
Block #73,923,773
7 transactions · 6 stateful · 2026-05-11 16:28:04 UTC
Parallelism
71
/100
Blocked
33
%
Avg conflicts / tx
0.29
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,923,773
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x6c05cd2b
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#3
0x5de3085d
#4
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0x3e1523…94aa
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0xe4b00f4b…34c0
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x3e1523…94aa
4 touches
1 conflict
0xed385e36…0251
0x7b2728…7777
4 touches
1 conflict
0x59658b83…2226
0x1b6862…e19c
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
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:
0x3e1523b2…8994aa
1 conflict on slot
0x0000000000…000003
Audit this contract →
← previous block
·
next block →
recent activity