pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,642,867
← previous block
next block →
recent activity
Analyzing
Block #73,642,867
9 transactions · 9 stateful · 2026-05-10 09:03:08 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,642,867
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
· blocks 1
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x98717539
#5
0x98717539
· blocks 1
#8
setData
#6
0x98717539
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe89e1a22…ce49
0x8d66a4…3095
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x0520da1d…c88e
0x34b655…2a6f
4 touches
1 conflict
0xa8bd52b5…862e
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1ab
0x8d66a4…3095
4 touches
1 conflict
0xc5564f8e…f4bf
0x6c4bfa…a540
2 touches
0 conflicts
0x414e6d08…fe12
0x065c9d…c394
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:
Perpl: Oracle / Operator Hub
1 conflict on slot
0xe89e1a2242…33ce49
Audit this contract →
← previous block
·
next block →
recent activity