pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#77,182,532
← previous block
next block →
recent activity
Analyzing
Block #77,182,532
12 transactions · 8 stateful · 2026-05-26 18:44:02 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,182,532
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
withdraw
#6
0x3f5c179b
#7
0x62be7533
#9
forward
#10
setData
#11
0x39435dac
#8
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0xb4766884…3b7e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1b293066…a69b
0x065c9d…c394
3 touches
1 conflict
0x3da78bb9…6ebd
0x065c9d…c394
3 touches
1 conflict
0xa4807b72…8130
0x065c9d…c394
3 touches
1 conflict
0x00000000…0001
0x010592…1c83
2 touches
0 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
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
0x95523e2aaf…734c01
Audit this contract →
← previous block
·
next block →
recent activity