pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,187,519
← previous block
next block →
recent activity
Analyzing
Block #73,187,519
9 transactions · 8 stateful · 2026-05-08 06:32:18 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,187,519
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x9609049f
· blocks 1
#3
0x39435dac
#5
updateDataFeedsValuesPartial
#6
0x69fd83ea
#7
setData
#8
0x39435dac
#2
0x121eab2f
· blocks 1
#4
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a354a63…0515
0x065c9d…c394
4 touches
1 conflict
0x70b2f813…783c
0x2a68ba…90c5
4 touches
1 conflict
0x8e66da19…66b6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1d5cfbc2…3083
0x065c9d…c394
3 touches
1 conflict
0x31a80474…3130
0x065c9d…c394
3 touches
1 conflict
0x5419a3d6…78d7
0x065c9d…c394
3 touches
1 conflict
0x9006e18c…acbf
0x065c9d…c394
3 touches
1 conflict
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
0x2a354a6333…480515
Audit this contract →
← previous block
·
next block →
recent activity