pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,307,916
← previous block
next block →
recent activity
Analyzing
Block #73,307,916
8 transactions · 7 stateful · 2026-05-08 19:53:15 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,307,916
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
setData
#3
0x121eab2f
#4
0x98717539
· blocks 1
#6
0x69fe3fa2
#7
0xeffdedb0
#5
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f430e47…4cbd
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a9
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ad
0x8d66a4…3095
4 touches
1 conflict
0xa94cf3f4…554c
0x8d66a4…3095
4 touches
1 conflict
0x4f91fd62…d68e
0x065c9d…c394
2 touches
0 conflicts
0x54578272…3aae
0x065c9d…c394
2 touches
0 conflicts
0x74525031…ac86
0x065c9d…c394
2 touches
0 conflicts
0x81d2e592…76e1
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
0x7f430e471f…4e4cbd
Audit this contract →
← previous block
·
next block →
recent activity