pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,163,045
← previous block
next block →
recent activity
Analyzing
Block #75,163,045
12 transactions · 9 stateful · 2026-05-17 10:16:30 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,163,045
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#2
addLiquidity
#3
0x98717539
#4
0x6a0995f5
#6
forward
#7
updateDataFeedsValuesPartial
#8
setData
#9
0xb2e07a…fbeb
#10
0xa2ccab…84c6
#11
0x39435dac
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x6003cc55…2cb7
0x065c9d…c394
2 touches
0 conflicts
0xaf159d50…2fbf
0x065c9d…c394
2 touches
0 conflicts
0xc133bfef…8999
0x065c9d…c394
2 touches
0 conflicts
0x438cf5f6…f077
0x2a68ba…90c5
2 touches
0 conflicts
0x968bdacb…f461
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
0xf3d7a307cc…f14d63
Audit this contract →
← previous block
·
next block →
recent activity