pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,210,543
← previous block
next block →
recent activity
Analyzing
Block #73,210,543
8 transactions · 8 stateful · 2026-05-08 09:05:32 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,210,543
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x39435dac
#4
setData
#5
forward
#6
updateDataFeedsValuesPartial
#7
0xeffdedb0
#3
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bcd90e8…5673
0x065c9d…c394
4 touches
1 conflict
0xce7bfe5e…5e58
0x065c9d…c394
4 touches
1 conflict
0xffc5cd88…2870
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x195e0b23…1a93
0x065c9d…c394
3 touches
1 conflict
0x51f9bad9…4350
0x065c9d…c394
3 touches
1 conflict
0xce146c46…05e5
0x065c9d…c394
3 touches
1 conflict
0xa638fbca…4285
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:
0x065c9d28…a9c394
1 conflict on slot
0x8bcd90e850…f35673
Audit this contract →
← previous block
·
next block →
recent activity