pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,655,067
← previous block
next block →
recent activity
Analyzing
Block #73,655,067
9 transactions · 9 stateful · 2026-05-10 10:25:20 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,655,067
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
· blocks 1
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
setData
#6
forward
#7
claimRewards
#8
0x6a005d87
#2
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed57bddf…1abf
0xc8689a…ee79
4 touches
1 conflict
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0x547faed5…f219
0x065c9d…c394
4 touches
1 conflict
0xde03553a…2510
0x065c9d…c394
4 touches
1 conflict
0xe48b0689…4b3d
0x065c9d…c394
4 touches
1 conflict
0xc9e97522…3519
0x2a68ba…90c5
4 touches
1 conflict
0x1a4b4152…0a08
0x6c4bfa…a540
4 touches
1 conflict
0x2e2214a9…fe0d
0x6c4bfa…a540
4 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:
0xc8689a47…62ee79
1 conflict on slot
0xed57bddf8e…bd1abf
Audit this contract →
← previous block
·
next block →
recent activity