pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,678,561
← previous block
next block →
recent activity
Analyzing
Block #90,678,561
7 transactions · 7 stateful · 2026-07-27 04:39:51 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,678,561
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x3f5c179b
#4
execFwdPositionOps
#5
setData
#6
execOrders
#2
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x21898044…a071
0x065c9d…c394
2 touches
0 conflicts
0x61dd6442…3cb2
0x065c9d…c394
2 touches
0 conflicts
0x9ce2f8bf…293c
0x065c9d…c394
2 touches
0 conflicts
0xc7a96415…c0be
0x065c9d…c394
2 touches
0 conflicts
0xef5a5ed8…a7ec
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
0x80afd9d9f2…3f57cf
Audit this contract →
← previous block
·
next block →
recent activity