pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,984,285
← previous block
next block →
recent activity
Analyzing
Block #72,984,285
12 transactions · 11 stateful · 2026-05-07 08:00:11 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,984,285
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
execute
#4
0xe7be4706
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x9e76c652
#8
0x69fc4703
#9
0xeffdedb0
#10
setData
#11
0x39435dac
#2
0x1094dc9f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0xb02793…e402
4 touches
1 conflict
0x00000000…0003
0xb02793…e402
4 touches
1 conflict
0x00000000…0004
0xb02793…e402
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xa980598e…ec52
0x3bd359…433a
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xcd510377…571e
0xee8c0e…1242
4 touches
1 conflict
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:
0xb02793fe…75e402
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity