pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,641,916
← previous block
next block →
recent activity
Analyzing
Block #73,641,916
9 transactions · 8 stateful · 2026-05-10 08:56:42 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,641,916
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x6a0048c2
#5
setData
#6
execute
#7
0x39435dac
· blocks 1
#2
0x98717539
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe89e1a22…ce49
0x8d66a4…3095
4 touches
1 conflict
0x0520da1d…c88e
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x689cd5fd…5556
0x34b655…2a6f
4 touches
1 conflict
0x9cc607d0…c9c7
0x34b655…2a6f
4 touches
1 conflict
0xa8bd52b5…862e
0x34b655…2a6f
4 touches
1 conflict
0xac206e47…ef7d
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1ab
0x8d66a4…3095
4 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:
0x8d66a43f…113095
1 conflict on slot
0xe89e1a2242…33ce49
Audit this contract →
← previous block
·
next block →
recent activity