pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,925,993
← previous block
next block →
recent activity
Analyzing
Block #73,925,993
10 transactions · 9 stateful · 2026-05-11 16:42:51 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,925,993
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#4
spin
#5
0xe7be4706
#6
updateDataFeedsValuesPartial
#7
forward
#8
setData
#9
jMMeC
#2
0x0c7abd22
· blocks 1
#3
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x099c425c…4e96
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x580c6fe7…0fe3
0x1b6862…e19c
4 touches
1 conflict
0xb3870dbe…bef3
0x2a68ba…90c5
4 touches
1 conflict
0xf0197e37…17d4
0x065c9d…c394
3 touches
1 conflict
0x3f784c90…44d7
0x065c9d…c394
2 touches
0 conflicts
0x48f44e4c…6e89
0x065c9d…c394
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:
0xd32edf66…9fff58
3 conflicts on slot
0x099c425c5a…474e96
Audit this contract →
← previous block
·
next block →
recent activity