pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,214,744
← previous block
next block →
recent activity
Analyzing
Block #73,214,744
9 transactions · 9 stateful · 2026-05-08 09:33:22 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,214,744
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x84396f10
#2
updatePosition
#3
updateDataFeedsValuesPartial
#4
0x5339c59f
· blocks 1
#6
0xeffdedb0
#7
setData
#8
0x785f5745
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x06956408…967b
0x754704…b603
2 touches
0 conflicts
0x1822932b…24a1
0x754704…b603
2 touches
0 conflicts
0xb30d9b95…3bf3
0x754704…b603
2 touches
0 conflicts
0xfd4bd0e6…5918
0x754704…b603
2 touches
0 conflicts
0x00000000…0009
0xae0830…85fe
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
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity