pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#71,289,754
← previous block
next block →
recent activity
Analyzing
Block #71,289,754
7 transactions · 5 stateful · 2026-04-29 11:41:46 UTC
Parallelism
57
/100
Blocked
60
%
Avg conflicts / tx
0.71
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,289,754
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x20601463
· blocks 3
#3
updateDataFeedsValuesPartial
#6
setData
#2
0x0c7abd22
· blocks 1
#4
0xed82b078
· blocks 1
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe2bac2b…2cec
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x01ef0c25…cb8c
0x065c9d…c394
2 touches
0 conflicts
0x03b1049a…0cb2
0x065c9d…c394
2 touches
0 conflicts
0x8e148af2…04bf
0x065c9d…c394
2 touches
0 conflicts
0xe7e6f855…f68f
0x065c9d…c394
2 touches
0 conflicts
0xeff22600…294e
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
3 conflicts on slot
0xfe2bac2b2f…482cec
Audit this contract →
← previous block
·
next block →
recent activity