pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,211,917
← previous block
next block →
recent activity
Analyzing
Block #73,211,917
8 transactions · 7 stateful · 2026-05-08 09:14:36 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,211,917
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0xed82b078
· blocks 1
#4
0xed82b078
#5
updateDataFeedsValuesPartial
#6
0x69fda9f4
#7
setData
#3
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce7bfe5e…5e58
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8e352fad…ea05
0x000000…012a
2 touches
0 conflicts
0x9b2c9a8b…cec7
0x000000…012a
2 touches
0 conflicts
0x1c9e5f70…b1c1
0x09475a…400f
2 touches
0 conflicts
0x5cdc8924…c0f1
0x10aeaf…5417
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
0xce7bfe5ef1…205e58
Audit this contract →
← previous block
·
next block →
recent activity