pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,176,119
← previous block
next block →
recent activity
Analyzing
Block #73,176,119
19 transactions · 16 stateful · 2026-05-08 05:16:15 UTC
Parallelism
84
/100
Blocked
13
%
Avg conflicts / tx
0.16
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,176,119
· 19 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#2
execute
#3
exactOutputSingle
#4
exactOutputSingle
#5
execute
#6
updatePrices
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#11
0x5339c59f
#12
0x5339c59f
#13
0x5339c59f
#14
0x69fd7217
#15
markGameAsLost
#16
setData
#17
0x80d8a7…f588
#18
0xa5057a…e90d
#9
0x5339c59f
· blocks 1
#10
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92500635…0b95
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x8e66da19…66b6
0x065c9d…c394
4 touches
1 conflict
0xca3a3472…8d68
0x065c9d…c394
3 touches
1 conflict
0xfb092a3a…142f
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x9250063573…0b0b95
Audit this contract →
← previous block
·
next block →
recent activity