pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,470,653
← previous block
next block →
recent activity
Analyzing
Block #76,470,653
10 transactions · 9 stateful · 2026-05-23 11:44:34 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,470,653
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
updateDataFeedsValuesPartial
#3
0x6c05cd2b
· blocks 1
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
setData
#8
execOrders
· blocks 1
#4
0xccf50a51
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0xe5a8f8…d7a8
4 touches
1 conflict
0x00000000…0004
0x126b3d…d8fe
4 touches
1 conflict
0x127cd6fe…36c5
0x21e325…7777
4 touches
1 conflict
0xbc467e7a…af36
0x21e325…7777
4 touches
1 conflict
0x9e719c7a…df63
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xae3fbd28…a18c
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0xe5a8f8…d7a8
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:
0xe5a8f88c…7dd7a8
1 conflict on slot
0x0000000000…000003
Audit this contract →
← previous block
·
next block →
recent activity