pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#77,240,579
← previous block
next block →
recent activity
Analyzing
Block #77,240,579
21 transactions · 12 stateful · 2026-05-27 01:13:48 UTC
Parallelism
90
/100
Blocked
8
%
Avg conflicts / tx
0.05
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,240,579
· 21 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x719d975a
· blocks 1
#2
0xa96df62f
#3
0x02712c64
#4
0x06712c64
#5
0x0a7d3bce
#6
0x0b3f51f6
#7
0x6c05cd2b
#8
execPerpOps
#9
execPerpOps
#11
updateDataFeedsValuesPartial
#12
0x3f5c179b
#13
updateDataFeedsValuesPartial
#14
updateDataFeedsValuesPartial
#15
execFwdPositionOps
#16
execFwdPositionOps
#17
setData
#18
setApprovalForAll
#19
jMMeC
#20
jMMeC
#10
0x000000b2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x7d3bce…1f9b
4 touches
1 conflict
0xbfe69c69…b2c4
0xd03f87…7691
4 touches
1 conflict
0x3107b7ef…3e93
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x7d3bce…1f9b
4 touches
1 conflict
0x6cb16a34…2e1c
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0xf5628e…e591
4 touches
1 conflict
0xb02cdac2…cf11
0xbc51ff…0f54
4 touches
1 conflict
0x00000000…0004
0xf5628e…e591
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:
0x7d3bce23…5c1f9b
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity