pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,923,034
← previous block
next block →
recent activity
Analyzing
Block #73,923,034
9 transactions · 6 stateful · 2026-05-11 16:23:08 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,923,034
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
· blocks 1
#2
0xd4f337…8b54
#3
0x6a0202e4
#4
addLiquidity
#5
updateDataFeedsValuesPartial
#6
forward
#8
setData
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x16354ba5…48c4
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ae46eb0…8357
0x065c9d…c394
2 touches
0 conflicts
0x0cb9d922…42ad
0x065c9d…c394
2 touches
0 conflicts
0x0d21c210…863d
0x065c9d…c394
2 touches
0 conflicts
0x54638670…c819
0x065c9d…c394
2 touches
0 conflicts
0x6f08361d…bda6
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity