pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,701,776
← previous block
next block →
recent activity
Analyzing
Block #75,701,776
11 transactions · 11 stateful · 2026-05-19 22:22:31 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,701,776
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1094dc9f
#2
0x6a0ce31e
#3
0xa96df62f
#4
0xe7be4706
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x39435dac
· blocks 1
#8
setData
#10
jMMeC
#7
0x5339c59f
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w0
7
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x37d16462…2847
0x065c9d…c394
3 touches
1 conflict
0x99f666e3…b2a2
0x3bd359…433a
2 touches
0 conflicts
0xfe3bddd2…8b48
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0003
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0005
0x5afd3e…7620
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
0xcc4f1f1446…7caa5f
Audit this contract →
← previous block
·
next block →
recent activity