pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,283,457
← previous block
next block →
recent activity
Analyzing
Block #72,283,457
12 transactions · 12 stateful · 2026-05-04 02:10:03 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,283,457
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
0x98c01e2a
#4
0x98717539
· blocks 2
#7
updateDataFeedsValuesPartial
#8
0x3f5c179b
#9
forward
#10
setData
#11
0x39435dac
#5
0x98717539
· blocks 1
#6
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x893cd52c…5766
0x34b655…2a6f
4 touches
1 conflict
0xcc6521c1…c892
0x8d66a4…3095
3 touches
1 conflict
0x8a35acfb…d1ac
0x8d66a4…3095
3 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
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:
0x34b6552d…112a6f
3 conflicts on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity