pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,425,812
← previous block
next block →
recent activity
Analyzing
Block #74,425,812
8 transactions · 6 stateful · 2026-05-14 00:10:28 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,425,812
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swapExactIn
· blocks 1
#3
0xed82b078
#4
get_block_hash_257335279069929
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x39435dac
#2
swapExactIn
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c885dad…7353
0x699abc…6a3b
4 touches
1 conflict
0xe7b759ce…105f
0x699abc…6a3b
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x194f2c02…19e6
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x28c180e1…f1e2
0x34b655…2a6f
2 touches
0 conflicts
0x8a51444d…223c
0x34b655…2a6f
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:
0x699abc15…c86a3b
1 conflict on slot
0x9c885dadd3…217353
Audit this contract →
← previous block
·
next block →
recent activity