pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,094,695
← previous block
next block →
recent activity
Analyzing
Block #72,094,695
7 transactions · 6 stateful · 2026-05-03 05:06:08 UTC
Parallelism
57
/100
Blocked
33
%
Avg conflicts / tx
0.43
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,094,695
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x98717539
· blocks 2
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x0c7abd22
#2
0x98717539
· blocks 1
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1ad
0x8d66a4…3095
6 touches
3 conflicts
0x8a35acfb…d1ac
0x8d66a4…3095
4 touches
1 conflict
0x96504a63…52d2
0x8d66a4…3095
4 touches
1 conflict
0x462c8be7…4f83
0x8d66a4…3095
4 touches
1 conflict
0xe96c91d2…32ff
0x8d66a4…3095
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
2 touches
0 conflicts
0xac808a27…82db
0x34b655…2a6f
2 touches
0 conflicts
0x143dba04…1b98
0x8d66a4…3095
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:
0x8d66a43f…113095
3 conflicts on slot
0x8a35acfbc1…6bd1ad
Audit this contract →
← previous block
·
next block →
recent activity