pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,023,858
← previous block
next block →
recent activity
Analyzing
Block #75,023,858
8 transactions · 7 stateful · 2026-05-16 18:47:54 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,023,858
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x98717539
#4
0x39435dac
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#2
0xed82b078
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7322a8d1…c0da
0x065c9d…c394
3 touches
1 conflict
0x8ec63087…24e8
0x065c9d…c394
3 touches
1 conflict
0x360a6eb1…376a
0x065c9d…c394
2 touches
0 conflicts
0x6c215fb1…481a
0x065c9d…c394
2 touches
0 conflicts
0x7903a00e…e915
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
0x348fda08cf…fc7e96
Audit this contract →
← previous block
·
next block →
recent activity