pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,652,075
← previous block
next block →
recent activity
Analyzing
Block #73,652,075
6 transactions · 5 stateful · 2026-05-10 10:05:07 UTC
Parallelism
50
/100
Blocked
40
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,652,075
· 6 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x42dd8743
· blocks 1
#2
updateDataFeedsValuesPartial
#5
setData
#3
0xed82b078
· blocks 1
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2e58b24b…820d
0x065c9d…c394
2 touches
0 conflicts
0xa4e3b3b1…0911
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0000
0x35aa76…fd64
2 touches
0 conflicts
0x00000000…0001
0x35aa76…fd64
2 touches
0 conflicts
0x00000000…0002
0x35aa76…fd64
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:
0x2a68ba18…8e90c5
1 conflict on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity