pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,333,684
← previous block
next block →
recent activity
Analyzing
Block #73,333,684
12 transactions · 9 stateful · 2026-05-08 22:44:44 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,333,684
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
· blocks 1
#2
0x98717539
#3
approve
#4
0x0c7abd22
#5
0xed82b078
#7
0xed82b078
#8
updateDataFeedsValuesPartial
#9
0x69fe67d3
#10
0xeffdedb0
#11
setData
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x25493bf5…99c4
0x065c9d…c394
2 touches
0 conflicts
0x25fbcec0…e18c
0x065c9d…c394
2 touches
0 conflicts
0x2ff9745d…ee70
0x065c9d…c394
2 touches
0 conflicts
0x3c16c902…2961
0x065c9d…c394
2 touches
0 conflicts
0x51bc5ce3…ac39
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity