pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,296,382
← previous block
next block →
recent activity
Analyzing
Block #72,296,382
10 transactions · 9 stateful · 2026-05-04 03:36:51 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,296,382
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
addLiquidity
#2
fillRelay
#3
0x9036287a
· blocks 1
#4
0x98717539
#5
updateDataFeedsValuesPartial
#7
forward
#8
0x69f814cb
#9
setData
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2e97fbb3…3089
0x065c9d…c394
4 touches
1 conflict
0x25757fa3…63ef
0x065c9d…c394
4 touches
1 conflict
0x1fa31ef1…23f0
0x065c9d…c394
3 touches
1 conflict
0xcd2768dc…3e26
0x065c9d…c394
3 touches
1 conflict
0x8c271b39…a6fc
0x065c9d…c394
3 touches
1 conflict
0xa57a54c6…fd81
0x065c9d…c394
3 touches
1 conflict
0x4039b31f…0f4a
0x754704…b603
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity