pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,501,361
← previous block
next block →
recent activity
Analyzing
Block #72,501,361
7 transactions · 5 stateful · 2026-05-05 02:22:18 UTC
Parallelism
71
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,501,361
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x98717539
#3
0xfa6fda…0de3
#5
updateDataFeedsValuesPartial
#6
setData
#4
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe8735a84…9d0f
0x065c9d…c394
4 touches
1 conflict
0x699c41f5…0cb8
0x065c9d…c394
4 touches
1 conflict
0xd8599661…975d
0x065c9d…c394
4 touches
1 conflict
0x9f73ebba…0ad5
0x065c9d…c394
3 touches
1 conflict
0x93213acb…0fa7
0x065c9d…c394
3 touches
1 conflict
0xf78c6abd…ce5e
0x065c9d…c394
3 touches
1 conflict
0x5f7474ee…ea21
0x065c9d…c394
3 touches
1 conflict
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