pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#77,434,810
← previous block
next block →
recent activity
Analyzing
Block #77,434,810
10 transactions · 9 stateful · 2026-05-27 22:47:58 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,434,810
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
· blocks 2
#4
0x6a177516
#5
swap
· blocks 1
#6
updateDataFeedsValuesPartial
#8
setData
#9
execOrders
#3
0xab083028
· blocks 1
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xda693078…02d1
0xa6afd3…d132
6 touches
3 conflicts
0x8bc3e255…0a0b
0xa6afd3…d132
6 touches
3 conflicts
0x10d80fee…dbda
0x69df8a…6292
4 touches
1 conflict
0xdf708ee7…1fcf
0xc8689a…ee79
4 touches
1 conflict
0xa4e3b3b1…0911
0x2a68ba…90c5
4 touches
1 conflict
0x10abefc9…c9bc
0x69df8a…6292
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
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-WETH/USDC
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity