pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,288,012
← previous block
next block →
recent activity
Analyzing
Block #72,288,012
11 transactions · 9 stateful · 2026-05-04 02:40:42 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,288,012
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
0xcf7468f4
#3
repay
#4
0x1094dc9f
· blocks 1
#5
0x0c7abd22
· blocks 1
#8
updateDataFeedsValuesPartial
#9
0x69f807a1
#10
setData
#6
0x3f5c179b
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0xc8bc8dc3…98db
0x065c9d…c394
3 touches
1 conflict
0xd1636ba4…2407
0xd32edf…ff58
3 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0x00000000…003a
0x3aca28…1526
2 touches
0 conflicts
0x71536dfc…aa0e
0x3aca28…1526
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
0xc3c8642ae9…317da5
Audit this contract →
← previous block
·
next block →
recent activity