pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#72,171,793
← previous block
next block →
recent activity
Analyzing
Block #72,171,793
10 transactions · 9 stateful · 2026-05-03 13:39:41 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,171,793
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#2
0x719d975a
#4
updatePrices
#5
updateDataFeedsValuesPartial
#7
updatePosition
#8
0x69f75094
#9
setData
#3
0x05ee6a22
· blocks 1
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0xcd30dde4…3072
0x065c9d…c394
5 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c5
0x1b6862…e19c
2 touches
0 conflicts
0x4bef88e0…eaca
0x3bd359…433a
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
3 conflicts on slot
0x92d610a6f9…379a40
Audit this contract →
← previous block
·
next block →
recent activity