pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,337,765
← previous block
next block →
recent activity
Analyzing
Block #73,337,765
12 transactions · 11 stateful · 2026-05-08 23:11:50 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,337,765
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69fe6e2e
#2
removeLiquidity
#3
updatePrices
· blocks 1
#5
0x5bf9264c
#6
0x5bf9264c
#7
0x121eab2f
· blocks 1
#9
0x98717539
#10
0xeffdedb0
#11
setData
#4
updatePrices
#8
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab4b6c67…fde9
0x065c9d…c394
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x00000000…000b
0xaba216…a862
4 touches
1 conflict
0x3e4b8d9f…b8a7
0xaba216…a862
4 touches
1 conflict
0xe7535190…5a0f
0xaba216…a862
4 touches
1 conflict
0xe94e77ab…f017
0xaba216…a862
4 touches
1 conflict
0xd821ae10…fe17
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:
0x065c9d28…a9c394
1 conflict on slot
0xab4b6c67aa…4ffde9
Audit this contract →
← previous block
·
next block →
recent activity