pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,223,888
← previous block
next block →
recent activity
Analyzing
Block #74,223,888
8 transactions · 7 stateful · 2026-05-13 01:47:14 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
#74,223,888
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x1ffa3c9b
· blocks 1
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
0x6a03d89a
#7
setData
#3
0xed82b078
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
0xbb7510f1…fa7a
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd8001c09…b42c
0x065c9d…c394
3 touches
1 conflict
0x87567e4b…734a
0x065c9d…c394
2 touches
0 conflicts
0xc65f5102…fbb6
0x065c9d…c394
2 touches
0 conflicts
0xe1a8faf1…ffae
0x065c9d…c394
2 touches
0 conflicts
0xe505d91c…eb7f
0x065c9d…c394
2 touches
0 conflicts
0xe61941b7…a99f
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
0xbb7510f188…cafa7a
Audit this contract →
← previous block
·
next block →
recent activity