pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#71,743,371
← previous block
next block →
recent activity
Analyzing
Block #71,743,371
10 transactions · 10 stateful · 2026-05-01 14:07:12 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,743,371
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute_route
· blocks 1
#3
0x575c0012
#5
0xeffdedb0
#6
0x3f5c179b
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
#2
execute_route
· blocks 1
#4
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x08943ea2…ed03
0x754704…b603
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0xd19f9d56…9330
0x3bd359…433a
2 touches
0 conflicts
0xd77e90ec…8c04
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x63e48b…53f2
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:
0x188d586d…f9ea8e
1 conflict on slot
0x01e7b86585…4d6e6d
Audit this contract →
← previous block
·
next block →
recent activity