pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,022,018
← previous block
next block →
recent activity
Analyzing
Block #75,022,018
5 transactions · 3 stateful · 2026-05-16 18:35:42 UTC
Parallelism
60
/100
Blocked
33
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,022,018
· 5 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setData
#2
0x1ffa3c9b
· blocks 1
#4
0xed82b078
#3
0x0c7abd22
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
0x0ae4c4c7…f875
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x62d6f012…c9dd
0x065c9d…c394
3 touches
1 conflict
0x0fc89c6b…696f
0x065c9d…c394
3 touches
1 conflict
0x1a683395…fcaa
0x065c9d…c394
2 touches
0 conflicts
0x2930103b…5f35
0x065c9d…c394
2 touches
0 conflicts
0x2adfc87b…c649
0x065c9d…c394
2 touches
0 conflicts
0x4eb1f171…b075
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
0x0ae4c4c78f…15f875
Audit this contract →
← previous block
·
next block →
recent activity