pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,693,573
← previous block
next block →
recent activity
Analyzing
Block #73,693,573
7 transactions · 6 stateful · 2026-05-10 14:45:07 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,693,573
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x121eab2f
· blocks 1
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
setData
#3
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e2214a9…fe0d
0x6c4bfa…a540
4 touches
1 conflict
0xe7535190…5a0f
0x6c4bfa…a540
4 touches
1 conflict
0xe94e77ab…f017
0x6c4bfa…a540
4 touches
1 conflict
0xae69c125…2379
0x2a68ba…90c5
4 touches
1 conflict
0xc9e97522…3519
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…000b
0x6c4bfa…a540
4 touches
1 conflict
0x3e4b8d9f…b8a7
0x6c4bfa…a540
4 touches
1 conflict
0xed57bddf…1abf
0xc8689a…ee79
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:
0x6c4bfa5a…81a540
1 conflict on slot
0x2e2214a9eb…b3fe0d
Audit this contract →
← previous block
·
next block →
recent activity