pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,337,753
← previous block
next block →
recent activity
Analyzing
Block #75,337,753
11 transactions · 9 stateful · 2026-05-18 05:44:41 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,337,753
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 2
#2
execPerpOps
#3
execPerpOps
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
0x0c7abd22
#9
setData
#10
jMMeC
#7
batchUpdate
#8
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x438cf5f6…f077
0x2a68ba…90c5
2 touches
0 conflicts
0x968bdacb…f461
0x2a68ba…90c5
2 touches
0 conflicts
0x0711ec2d…d973
0x34b655…2a6f
2 touches
0 conflicts
0x15698ac9…2a46
0x34b655…2a6f
2 touches
0 conflicts
0x414e9446…4b59
0x34b655…2a6f
2 touches
0 conflicts
0x4480f7dc…e785
0x34b655…2a6f
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
0x443a3e479f…3af4a4
Audit this contract →
← previous block
·
next block →
recent activity